Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ad837d8dcc69fb7c58c944a63d09d713f2e82c2a8d9bf6686bc2533c7ab9072

Tx prefix hash: 59a2609835c5814c7d76cc399a21def9b1ef234eb84441eff59ed2ef52a105c2
Tx public key: bf70bf6ebfc3a316e1041a2bd65c06255364f26af7de780303308966f0d4d7c0
Timestamp: 1755828551 Timestamp [UCT]: 2025-08-22 02:09:11 Age [y:d:h:m:s]: 00:068:15:52:49
Block: 1351668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48993 RingCT/type: yes/0
Extra: 01bf70bf6ebfc3a316e1041a2bd65c06255364f26af7de780303308966f0d4d7c002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b89b611c0562cb2f5c0f1c9c1eb984c42aab46d1d58356fd86dff705766d82e 0.600000000000 1839625 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": 1351678, "vin": [ { "gen": { "height": 1351668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b89b611c0562cb2f5c0f1c9c1eb984c42aab46d1d58356fd86dff705766d82e" } } ], "extra": [ 1, 191, 112, 191, 110, 191, 195, 163, 22, 225, 4, 26, 43, 214, 92, 6, 37, 83, 100, 242, 106, 247, 222, 120, 3, 3, 48, 137, 102, 240, 212, 215, 192, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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