Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7386440baf2c251d54aa890737c632b9c5b0762801569e1a17dcc478b75a9b40

Tx prefix hash: 84a0d4ce9bf5655b5459ac224acf76c9320a14f8d4bb8731a704202e34f78f1c
Tx public key: 8f2473208babb1d2dd48930f2cd9ae6084687ff84bb91f14741f97f7eb20c4a2
Timestamp: 1718929054 Timestamp [UCT]: 2024-06-21 00:17:34 Age [y:d:h:m:s]: 01:138:18:52:23
Block: 1048674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357729 RingCT/type: yes/0
Extra: 018f2473208babb1d2dd48930f2cd9ae6084687ff84bb91f14741f97f7eb20c4a202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb21e6e33e4a1a76f69e39f2f7f38a4cac5bd546476b172e6840671856b0b5a 0.600000000000 1518759 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1048684, "vin": [ { "gen": { "height": 1048674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb21e6e33e4a1a76f69e39f2f7f38a4cac5bd546476b172e6840671856b0b5a" } } ], "extra": [ 1, 143, 36, 115, 32, 139, 171, 177, 210, 221, 72, 147, 15, 44, 217, 174, 96, 132, 104, 127, 248, 75, 185, 31, 20, 116, 31, 151, 247, 235, 32, 196, 162, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8