Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b91598f2f2574b96dd0fafde23507348e65da9e90655f9ef564f67c86ec0b195

Tx prefix hash: 34aa2c096beba49cbc8672cb185026c3789debe39759db96b9c76493149a7b1e
Tx public key: 6e839ea716e9b2cb192fba0263dfeec72ece97d55ea08521669ab67f276b3ea8
Timestamp: 1713679324 Timestamp [UCT]: 2024-04-21 06:02:04 Age [y:d:h:m:s]: 01:193:02:05:12
Block: 1005148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396653 RingCT/type: yes/0
Extra: 016e839ea716e9b2cb192fba0263dfeec72ece97d55ea08521669ab67f276b3ea80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 208fa2dc2abc6d5e7e75225d34e08ffa28266fd8307cc71bbc4f8f1255187915 0.600000000000 1465728 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": 1005158, "vin": [ { "gen": { "height": 1005148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "208fa2dc2abc6d5e7e75225d34e08ffa28266fd8307cc71bbc4f8f1255187915" } } ], "extra": [ 1, 110, 131, 158, 167, 22, 233, 178, 203, 25, 47, 186, 2, 99, 223, 238, 199, 46, 206, 151, 213, 94, 160, 133, 33, 102, 154, 182, 127, 39, 107, 62, 168, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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