Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acc5a9db04ef8f095c78fa0c069035b91f8b2beec1c10abf12ee560846a9b842

Tx prefix hash: d4a58c9954dacd9802fa3b504af398f6fd0509c30cda42f288ba13d88e679813
Tx public key: a928f0ab528dea79a3d91be49cf061c72dc4e40c377cb71209d05bf7d62fc3b5
Timestamp: 1709415153 Timestamp [UCT]: 2024-03-02 21:32:33 Age [y:d:h:m:s]: 01:083:00:59:30
Block: 969812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320384 RingCT/type: yes/0
Extra: 01a928f0ab528dea79a3d91be49cf061c72dc4e40c377cb71209d05bf7d62fc3b50211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4406e2df79bec80e900375e26c111981b8fdf0bdafef331543ff9b8546cf8d70 0.600000000000 1429659 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": 969822, "vin": [ { "gen": { "height": 969812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4406e2df79bec80e900375e26c111981b8fdf0bdafef331543ff9b8546cf8d70" } } ], "extra": [ 1, 169, 40, 240, 171, 82, 141, 234, 121, 163, 217, 27, 228, 156, 240, 97, 199, 45, 196, 228, 12, 55, 124, 183, 18, 9, 208, 91, 247, 214, 47, 195, 181, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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