Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5515b855f95d6253781c3cc665ff0e446829353e4279fe562e1fad46dd7c3aaf

Tx prefix hash: eb6a6bd349b3d97c2c07f5f7e5e30875c7b1af0e5133366e1b8649cb5e169122
Tx public key: a2e4506ce694bac5002370937a66cb31755bbe3ea39e0d9e4c00f3c4eeebd292
Timestamp: 1762717144 Timestamp [UCT]: 2025-11-09 19:39:04 Age [y:d:h:m:s]: 00:011:02:48:16
Block: 1408583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7947 RingCT/type: yes/0
Extra: 01a2e4506ce694bac5002370937a66cb31755bbe3ea39e0d9e4c00f3c4eeebd292021100000005dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5ce7fc9efe473d7666fbe33b641b27ddad1c410294fbea1110fb79d29aa2795 0.600000000000 1897012 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": 1408593, "vin": [ { "gen": { "height": 1408583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5ce7fc9efe473d7666fbe33b641b27ddad1c410294fbea1110fb79d29aa2795" } } ], "extra": [ 1, 162, 228, 80, 108, 230, 148, 186, 197, 0, 35, 112, 147, 122, 102, 203, 49, 117, 91, 190, 62, 163, 158, 13, 158, 76, 0, 243, 196, 238, 235, 210, 146, 2, 17, 0, 0, 0, 5, 223, 195, 186, 73, 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