Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e6cd9aac9e1f54eaad8b304a1f3b158cbcf02ad954e16087d95615d03b99805

Tx prefix hash: 60940fcd6a390040a0c5e9dc9b24c286a75dc07789ab259366c0101f7f269de8
Tx public key: 3350ac34a91ef7dd78743a3bd095ae94ebe133f3ed75a401fd5fe6e0fdd890d2
Timestamp: 1724377684 Timestamp [UCT]: 2024-08-23 01:48:04 Age [y:d:h:m:s]: 01:073:05:55:36
Block: 1093861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310785 RingCT/type: yes/0
Extra: 013350ac34a91ef7dd78743a3bd095ae94ebe133f3ed75a401fd5fe6e0fdd890d202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ade2a6e1ea1e8cd5a5baad27da509b67c41a8d3cbbb132604c85737f6abbd437 0.600000000000 1568890 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": 1093871, "vin": [ { "gen": { "height": 1093861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ade2a6e1ea1e8cd5a5baad27da509b67c41a8d3cbbb132604c85737f6abbd437" } } ], "extra": [ 1, 51, 80, 172, 52, 169, 30, 247, 221, 120, 116, 58, 59, 208, 149, 174, 148, 235, 225, 51, 243, 237, 117, 164, 1, 253, 95, 230, 224, 253, 216, 144, 210, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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