Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3041cb9bf96ef164682da934fdb54799d6f947c4d051c4993ac9ca244e91389f

Tx prefix hash: 3a5dbb6991ef4e23001b7860111db65c3b6f38432ea0cae92e385e56251969ee
Tx public key: 07d0cffae261dbc1dfb8c6d803d620ff9dfc0471bb9b322ded8c98f487bdd61e
Timestamp: 1736718440 Timestamp [UCT]: 2025-01-12 21:47:20 Age [y:d:h:m:s]: 00:106:03:31:53
Block: 1196014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75667 RingCT/type: yes/0
Extra: 0107d0cffae261dbc1dfb8c6d803d620ff9dfc0471bb9b322ded8c98f487bdd61e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0de56ff17a364d687c2dba887e1508dd80ea2d30b7a3001b7eadde588a0a1456 0.600000000000 1682611 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": 1196024, "vin": [ { "gen": { "height": 1196014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0de56ff17a364d687c2dba887e1508dd80ea2d30b7a3001b7eadde588a0a1456" } } ], "extra": [ 1, 7, 208, 207, 250, 226, 97, 219, 193, 223, 184, 198, 216, 3, 214, 32, 255, 157, 252, 4, 113, 187, 155, 50, 45, 237, 140, 152, 244, 135, 189, 214, 30, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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