Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ffcf1bda0e20ea6a10ca9662d3b1da48d9b534ee84b85fb809b06a911e4589d

Tx prefix hash: 48db974cd67ea76e79feafbfd5542ba0b79a4332b780221e802cbd8070987ee8
Tx public key: 27c6dda973818274d56ecd87244f81268e9ef0e5ed73ed2ee3b0924d50c49804
Timestamp: 1728046237 Timestamp [UCT]: 2024-10-04 12:50:37 Age [y:d:h:m:s]: 00:161:12:05:02
Block: 1124270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115226 RingCT/type: yes/0
Extra: 0127c6dda973818274d56ecd87244f81268e9ef0e5ed73ed2ee3b0924d50c4980402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6706b79ac840543e2cb6c9c5d3088e64c6c1c1af713c49f0e0483b79f9701977 0.600000000000 1606879 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": 1124280, "vin": [ { "gen": { "height": 1124270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6706b79ac840543e2cb6c9c5d3088e64c6c1c1af713c49f0e0483b79f9701977" } } ], "extra": [ 1, 39, 198, 221, 169, 115, 129, 130, 116, 213, 110, 205, 135, 36, 79, 129, 38, 142, 158, 240, 229, 237, 115, 237, 46, 227, 176, 146, 77, 80, 196, 152, 4, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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