Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b0a603c762f3c01753fee63c2a2aa40183c0810ea11aeb8eee90ce0a2d36857

Tx prefix hash: 6dedf05fd9e8031fae6137a080488461eab12505d4cba7da792e43cc8cd84ebf
Tx public key: 0559843be0e501c8ed1354104612a345acd5f900cb31e1cb64837ea112e79129
Timestamp: 1762388330 Timestamp [UCT]: 2025-11-06 00:18:50 Age [y:d:h:m:s]: 00:084:07:33:24
Block: 1405838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60209 RingCT/type: yes/0
Extra: 010559843be0e501c8ed1354104612a345acd5f900cb31e1cb64837ea112e791290211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00e2e5a9182cd8dae9ae76b38e3c6df824ad73c9ae5e3dd64ef10a601032f051 0.600000000000 1894219 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": 1405848, "vin": [ { "gen": { "height": 1405838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00e2e5a9182cd8dae9ae76b38e3c6df824ad73c9ae5e3dd64ef10a601032f051" } } ], "extra": [ 1, 5, 89, 132, 59, 224, 229, 1, 200, 237, 19, 84, 16, 70, 18, 163, 69, 172, 213, 249, 0, 203, 49, 225, 203, 100, 131, 126, 161, 18, 231, 145, 41, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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