Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3987412f8ee25a2df2c7315d68680eed8fd4471e3e30b9fa085c640d6af5fe55

Tx prefix hash: a85f3aff4ef9e0d1695332ca73595af32a14b5eb89a6fe61c91cfea8ae7d963c
Tx public key: 8a1e1a8bd1bef973b0f0c3c3f108fbe3fe3011e907b88feedd414f1c5fd9c42d
Timestamp: 1757078999 Timestamp [UCT]: 2025-09-05 13:29:59 Age [y:d:h:m:s]: 00:083:02:16:14
Block: 1361933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59422 RingCT/type: yes/0
Extra: 018a1e1a8bd1bef973b0f0c3c3f108fbe3fe3011e907b88feedd414f1c5fd9c42d021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c75aa4846ca2542ab8fe72cc38864e9da61e9b69cd4411ca135ba7ee402dc76 0.600000000000 1849956 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": 1361943, "vin": [ { "gen": { "height": 1361933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c75aa4846ca2542ab8fe72cc38864e9da61e9b69cd4411ca135ba7ee402dc76" } } ], "extra": [ 1, 138, 30, 26, 139, 209, 190, 249, 115, 176, 240, 195, 195, 241, 8, 251, 227, 254, 48, 17, 233, 7, 184, 143, 238, 221, 65, 79, 28, 95, 217, 196, 45, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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