Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b4f5d14929eb94e22f41c8c9373146295eb415f5e0e054f36ca6c7f3998c2ce

Tx prefix hash: dfabd08a64ab4d1fc30f78ec6e05257cae97ae65767233c23527e253833e1cd3
Tx public key: b0f2711601c4099230e109a8cb49bb5aa9b03d262557524ac8362ed059faecf5
Timestamp: 1764241996 Timestamp [UCT]: 2025-11-27 11:13:16 Age [y:d:h:m:s]: 00:024:22:30:43
Block: 1421216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17849 RingCT/type: yes/0
Extra: 01b0f2711601c4099230e109a8cb49bb5aa9b03d262557524ac8362ed059faecf50211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd9c1389a1cd5918e508e96baa441f98d16cb96f7f009d5d87a518ccfa907f29 0.600000000000 1909773 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": 1421226, "vin": [ { "gen": { "height": 1421216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd9c1389a1cd5918e508e96baa441f98d16cb96f7f009d5d87a518ccfa907f29" } } ], "extra": [ 1, 176, 242, 113, 22, 1, 196, 9, 146, 48, 225, 9, 168, 203, 73, 187, 90, 169, 176, 61, 38, 37, 87, 82, 74, 200, 54, 46, 208, 89, 250, 236, 245, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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