Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5cfb11ace3838ec58bbcf2645b95ffcbc1d326f00d8b194f0c3804491a7e491

Tx prefix hash: bc0a3c2492e83f35529884d7f0af9032489eeee88317c907ed133275fa688421
Tx public key: ebc72b7e963997d89ea87a7a61d5d65aefd499bdd76876e934c4ea886c336b21
Timestamp: 1744431228 Timestamp [UCT]: 2025-04-12 04:13:48 Age [y:d:h:m:s]: 00:272:03:39:54
Block: 1259592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192316 RingCT/type: yes/0
Extra: 01ebc72b7e963997d89ea87a7a61d5d65aefd499bdd76876e934c4ea886c336b21021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a9f3fb36c1317cab5def116c9bed02ebc3b6777e0329867e91b13d41e6aeade 0.600000000000 1746739 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": 1259602, "vin": [ { "gen": { "height": 1259592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a9f3fb36c1317cab5def116c9bed02ebc3b6777e0329867e91b13d41e6aeade" } } ], "extra": [ 1, 235, 199, 43, 126, 150, 57, 151, 216, 158, 168, 122, 122, 97, 213, 214, 90, 239, 212, 153, 189, 215, 104, 118, 233, 52, 196, 234, 136, 108, 51, 107, 33, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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