Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f08ad7a646be0f8d71e95ba51bc3c3426210a1d163d165db4c217e337b1e59c

Tx prefix hash: 300d5d88ce770e5d1d4ac7aa835563f6d18930f437aa3378e361d075c72055cf
Tx public key: 27e7b77035453b197ade722dea7d6c1aec2384dffb329f20dca9430430feb0a5
Timestamp: 1744849620 Timestamp [UCT]: 2025-04-17 00:27:00 Age [y:d:h:m:s]: 00:211:04:18:58
Block: 1263061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148651 RingCT/type: yes/0
Extra: 0127e7b77035453b197ade722dea7d6c1aec2384dffb329f20dca9430430feb0a50211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6161237f2dd0e0b83ba5df4ca620a590d863f9c96b5dfaf28e6aa435bed054b 0.600000000000 1750244 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": 1263071, "vin": [ { "gen": { "height": 1263061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6161237f2dd0e0b83ba5df4ca620a590d863f9c96b5dfaf28e6aa435bed054b" } } ], "extra": [ 1, 39, 231, 183, 112, 53, 69, 59, 25, 122, 222, 114, 45, 234, 125, 108, 26, 236, 35, 132, 223, 251, 50, 159, 32, 220, 169, 67, 4, 48, 254, 176, 165, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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