Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53bcb61184457aeb148e3f7fda117d97618737d1703af45928fd8f48c8a9a5fe

Tx prefix hash: 8ee234c70994541aded02f4eba5868516c8eac95148dbb49739eaecbe5c9c4bb
Tx public key: 424923b6e92fce979219acaae6aa035ed9232e6a61fd414b9c7e58e3fb9eb1ff
Timestamp: 1762089391 Timestamp [UCT]: 2025-11-02 13:16:31 Age [y:d:h:m:s]: 00:062:02:44:21
Block: 1403376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44476 RingCT/type: yes/0
Extra: 01424923b6e92fce979219acaae6aa035ed9232e6a61fd414b9c7e58e3fb9eb1ff02110000000901491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e819bde22196e8597f4a742320931ee08800e087caefc32922759722fb67fb1d 0.600000000000 1891717 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": 1403386, "vin": [ { "gen": { "height": 1403376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e819bde22196e8597f4a742320931ee08800e087caefc32922759722fb67fb1d" } } ], "extra": [ 1, 66, 73, 35, 182, 233, 47, 206, 151, 146, 25, 172, 170, 230, 170, 3, 94, 217, 35, 46, 106, 97, 253, 65, 75, 156, 126, 88, 227, 251, 158, 177, 255, 2, 17, 0, 0, 0, 9, 1, 73, 31, 136, 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