Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fc731fc4c7df4cf622b7ab8c5b51e750da96a2d6e56843de8b819d84d0009fe

Tx prefix hash: 1a6114220780c8e90e591569942b13af93e66cf6213259c1b6e9374e146deb35
Tx public key: d4b797ab08b4c5f047e3f24bab80cdc81e183bd45eebd80033300324339b2dcb
Timestamp: 1714711169 Timestamp [UCT]: 2024-05-03 04:39:29 Age [y:d:h:m:s]: 00:249:12:23:55
Block: 1013716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178583 RingCT/type: yes/0
Extra: 01d4b797ab08b4c5f047e3f24bab80cdc81e183bd45eebd80033300324339b2dcb02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8a814e2a1613b9896526d6dee4d6e91831b96af15df211ecb0608d1d758411c 0.600000000000 1476607 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": 1013726, "vin": [ { "gen": { "height": 1013716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8a814e2a1613b9896526d6dee4d6e91831b96af15df211ecb0608d1d758411c" } } ], "extra": [ 1, 212, 183, 151, 171, 8, 180, 197, 240, 71, 227, 242, 75, 171, 128, 205, 200, 30, 24, 59, 212, 94, 235, 216, 0, 51, 48, 3, 36, 51, 155, 45, 203, 2, 17, 0, 0, 0, 3, 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