Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bf462e754528184a9ba5ea6955063694573299ce2c9e32a10ee1d149cdcd5d5

Tx prefix hash: b8c4dd4623bb25aa287e1b78f996dd95f23732ff752f1b07ad1451a74612e02a
Tx public key: df1b1bf9ff2fc1b2c5a4bbf6ddd6d88714adfbc48fb5bafa2a4ac5a9782f835a
Timestamp: 1714429682 Timestamp [UCT]: 2024-04-29 22:28:02 Age [y:d:h:m:s]: 00:304:10:56:26
Block: 1011363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217615 RingCT/type: yes/0
Extra: 01df1b1bf9ff2fc1b2c5a4bbf6ddd6d88714adfbc48fb5bafa2a4ac5a9782f835a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1f270847e1a083a971292e6d7c841ab13564d8f314da305a10f1d4d163b626b 0.600000000000 1473577 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": 1011373, "vin": [ { "gen": { "height": 1011363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1f270847e1a083a971292e6d7c841ab13564d8f314da305a10f1d4d163b626b" } } ], "extra": [ 1, 223, 27, 27, 249, 255, 47, 193, 178, 197, 164, 187, 246, 221, 214, 216, 135, 20, 173, 251, 196, 143, 181, 186, 250, 42, 74, 197, 169, 120, 47, 131, 90, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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