Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384c0f8dce694b76d97a6537b84fc7918b227004aa0c7fe1a52bb5c27fb90942

Tx prefix hash: 44ea32232bcbd7b53313383f4e666be50b96606cea975b66c2629ab907c9205e
Tx public key: 7aa11a09c13c19ec33177808e63c101d8f17bb4c6e2b9515e24b09bc17b39fc5
Timestamp: 1581515987 Timestamp [UCT]: 2020-02-12 13:59:47 Age [y:d:h:m:s]: 05:021:06:16:15
Block: 63527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167938 RingCT/type: yes/0
Extra: 017aa11a09c13c19ec33177808e63c101d8f17bb4c6e2b9515e24b09bc17b39fc5021100000002c71d3ff9000000000000000000

1 output(s) for total of 378.015398168000 dcy

stealth address amount amount idx
00: 1e0f4ce989f3716b0c3d7d5cf1ac6b8bd13a6f7f858e37e973cf02daaa536c47 378.015398168000 117095 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": 63537, "vin": [ { "gen": { "height": 63527 } } ], "vout": [ { "amount": 378015398168, "target": { "key": "1e0f4ce989f3716b0c3d7d5cf1ac6b8bd13a6f7f858e37e973cf02daaa536c47" } } ], "extra": [ 1, 122, 161, 26, 9, 193, 60, 25, 236, 51, 23, 120, 8, 230, 60, 16, 29, 143, 23, 187, 76, 110, 43, 149, 21, 226, 75, 9, 188, 23, 179, 159, 197, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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