Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 934e24ef2067b247dc845bb6ac97df485f41f357fe265d016da6845de4f9be57

Tx prefix hash: 6f499aac03d5025eae9a90fd86aa1a4bb4e19cd3a4cfef5635e196f363058e0e
Tx public key: 0b6cff976be38c2f7d8a269a71b63ba0ac3a3f49e132c295958f098dfe4a86a0
Timestamp: 1584923206 Timestamp [UCT]: 2020-03-23 00:26:46 Age [y:d:h:m:s]: 04:347:13:07:42
Block: 86956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145033 RingCT/type: yes/0
Extra: 010b6cff976be38c2f7d8a269a71b63ba0ac3a3f49e132c295958f098dfe4a86a002110000009c48d4d863000000000000000000

1 output(s) for total of 316.140004110000 dcy

stealth address amount amount idx
00: 8fce4697cc6a93c6368d8f3374f423bc909864697593052a907518ee1be4d43c 316.140004110000 156818 of 0

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": 86966, "vin": [ { "gen": { "height": 86956 } } ], "vout": [ { "amount": 316140004110, "target": { "key": "8fce4697cc6a93c6368d8f3374f423bc909864697593052a907518ee1be4d43c" } } ], "extra": [ 1, 11, 108, 255, 151, 107, 227, 140, 47, 125, 138, 38, 154, 113, 182, 59, 160, 172, 58, 63, 73, 225, 50, 194, 149, 149, 143, 9, 141, 254, 74, 134, 160, 2, 17, 0, 0, 0, 156, 72, 212, 216, 99, 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