Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030b06c3106f8e9891c26603c33348a89204203797ea56d4c8be449bc146943b

Tx prefix hash: 83d9e05ab9d4b7654c966b716322d0b4ad72b7dedcf869a9bfa11313ad4ce5dd
Tx public key: e2f660897da5d1e6000e41cacdb02d6e0e5e3fb1ae54ed45cea41ea6f4aea3e6
Timestamp: 1717243574 Timestamp [UCT]: 2024-06-01 12:06:14 Age [y:d:h:m:s]: 00:213:22:29:55
Block: 1034707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153106 RingCT/type: yes/0
Extra: 01e2f660897da5d1e6000e41cacdb02d6e0e5e3fb1ae54ed45cea41ea6f4aea3e602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09c097e3fb2b6cd21efcb8213346e5269945b7cfe39a90dc91b283f0b19d0560 0.600000000000 1503224 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": 1034717, "vin": [ { "gen": { "height": 1034707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09c097e3fb2b6cd21efcb8213346e5269945b7cfe39a90dc91b283f0b19d0560" } } ], "extra": [ 1, 226, 246, 96, 137, 125, 165, 209, 230, 0, 14, 65, 202, 205, 176, 45, 110, 14, 94, 63, 177, 174, 84, 237, 69, 206, 164, 30, 166, 244, 174, 163, 230, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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