Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e94fd1dd60f4a8ebf3af2ff6b8bc7a5558d7d1cd9228adf682ed0b59e24c1a8

Tx prefix hash: a09674fe6433e9d22a825b829f70d145db4a6963f8ea0de00d3e7d4dfc952db0
Tx public key: 1f39ddeaa27818f76ef170600e9b585f1c9e66d4cc3f7d6f2a1c8bcd8848398c
Timestamp: 1734365142 Timestamp [UCT]: 2024-12-16 16:05:42 Age [y:d:h:m:s]: 00:121:12:50:09
Block: 1176553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86645 RingCT/type: yes/0
Extra: 011f39ddeaa27818f76ef170600e9b585f1c9e66d4cc3f7d6f2a1c8bcd8848398c0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ba05002eba9d4d12a9796068151f8bc74be57cc40377b01761e3394f26c8057 0.600000000000 1662906 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": 1176563, "vin": [ { "gen": { "height": 1176553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ba05002eba9d4d12a9796068151f8bc74be57cc40377b01761e3394f26c8057" } } ], "extra": [ 1, 31, 57, 221, 234, 162, 120, 24, 247, 110, 241, 112, 96, 14, 155, 88, 95, 28, 158, 102, 212, 204, 63, 125, 111, 42, 28, 139, 205, 136, 72, 57, 140, 2, 17, 0, 0, 0, 5, 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