Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 370b94cea325f39c72244af2ac64cf07e22feed7a924e5141c4bb12fde78b53c

Tx prefix hash: 09ba2b9549c0b5b86af9f05d503c4a6a42d4e2f673c74336c4d12a8c68e8290d
Tx public key: 6e38beb67ec003b2783ddbde72fddff0642069a0742020dd50be17ba7d0a2196
Timestamp: 1582101647 Timestamp [UCT]: 2020-02-19 08:40:47 Age [y:d:h:m:s]: 04:284:01:17:34
Block: 68043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095436 RingCT/type: yes/0
Extra: 016e38beb67ec003b2783ddbde72fddff0642069a0742020dd50be17ba7d0a219602110000000356c366d3000000000000000000

1 output(s) for total of 365.212893550000 dcy

stealth address amount amount idx
00: 328547e312f4cfac610957c86e2b1bfead2b8c1b4a898df3f7f6109e591f1e4d 365.212893550000 125331 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": 68053, "vin": [ { "gen": { "height": 68043 } } ], "vout": [ { "amount": 365212893550, "target": { "key": "328547e312f4cfac610957c86e2b1bfead2b8c1b4a898df3f7f6109e591f1e4d" } } ], "extra": [ 1, 110, 56, 190, 182, 126, 192, 3, 178, 120, 61, 219, 222, 114, 253, 223, 240, 100, 32, 105, 160, 116, 32, 32, 221, 80, 190, 23, 186, 125, 10, 33, 150, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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