Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a641e578f357ae921ca2005fd0ac9e1a290c1a4d7a54292e0e5d1daf3f5fe1f

Tx prefix hash: bc57f91ec59d3a571c95d0a28d84cc057a4007e8c062758de2b82b1a3eb302e2
Tx public key: 5ea8fba4a8549ccbe58d9d5c7848d37356b6d8df94a10ced9541a7364dc14ec8
Timestamp: 1737378842 Timestamp [UCT]: 2025-01-20 13:14:02 Age [y:d:h:m:s]: 00:336:14:26:44
Block: 1201436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238168 RingCT/type: yes/0
Extra: 015ea8fba4a8549ccbe58d9d5c7848d37356b6d8df94a10ced9541a7364dc14ec8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3b0f9ba46b71d47826f325b96ce02fd0c52ef1915e9dc16e921362e147cc6a0 0.600000000000 1688089 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": 1201446, "vin": [ { "gen": { "height": 1201436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3b0f9ba46b71d47826f325b96ce02fd0c52ef1915e9dc16e921362e147cc6a0" } } ], "extra": [ 1, 94, 168, 251, 164, 168, 84, 156, 203, 229, 141, 157, 92, 120, 72, 211, 115, 86, 182, 216, 223, 148, 161, 12, 237, 149, 65, 167, 54, 77, 193, 78, 200, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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