Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dbe8f49c7e7062699c6fcb37384881255a68c9aba2392646951fcc3df2a92c6

Tx prefix hash: a1c2882c020f708fc638e7640b3ce7f884dbac2853eef1eadcf90564fe357be9
Tx public key: 6d31717dcd2ab6fa838cab83c3bee01d3b8cfe6c8d434b619ae04e2a47665757
Timestamp: 1736385088 Timestamp [UCT]: 2025-01-09 01:11:28 Age [y:d:h:m:s]: 00:091:02:19:35
Block: 1193261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64888 RingCT/type: yes/0
Extra: 016d31717dcd2ab6fa838cab83c3bee01d3b8cfe6c8d434b619ae04e2a476657570211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bacadf3f71fae48dbc88281ea6a2875cdca6a3523293732542a0c7b5061a33f5 0.600000000000 1679820 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": 1193271, "vin": [ { "gen": { "height": 1193261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bacadf3f71fae48dbc88281ea6a2875cdca6a3523293732542a0c7b5061a33f5" } } ], "extra": [ 1, 109, 49, 113, 125, 205, 42, 182, 250, 131, 140, 171, 131, 195, 190, 224, 29, 59, 140, 254, 108, 141, 67, 75, 97, 154, 224, 78, 42, 71, 102, 87, 87, 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