Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e061fdf71fd4b7ffad385e136dbd4e4eb1cf36968b1b357e30a1fcfc706212a

Tx prefix hash: 693d6573304c7d104b5d0bc091a40a23f8c11dc80849cf8e0013915b320b9c1f
Tx public key: e2b53e05ce6c66eb0f5c1390f3f8b8b2f12acb9ff7ca0e1b39cc16e6787521b7
Timestamp: 1763069811 Timestamp [UCT]: 2025-11-13 21:36:51 Age [y:d:h:m:s]: 00:039:16:48:02
Block: 1411502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28414 RingCT/type: yes/0
Extra: 01e2b53e05ce6c66eb0f5c1390f3f8b8b2f12acb9ff7ca0e1b39cc16e6787521b7021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05204c09e418baf3f305f6cd812fecc308a1b0d154ad8545455eec33c4b2d2aa 0.600000000000 1899963 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": 1411512, "vin": [ { "gen": { "height": 1411502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05204c09e418baf3f305f6cd812fecc308a1b0d154ad8545455eec33c4b2d2aa" } } ], "extra": [ 1, 226, 181, 62, 5, 206, 108, 102, 235, 15, 92, 19, 144, 243, 248, 184, 178, 241, 42, 203, 159, 247, 202, 14, 27, 57, 204, 22, 230, 120, 117, 33, 183, 2, 17, 0, 0, 0, 1, 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