Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 293e4c9d3b1110d1f68be4d18d86a9a9f7b87ae3f1f085bb2ad08794e4a774f0

Tx prefix hash: 66a931ec18ea0d48e7ea4042e5052bb0ee67266dfb7620cc42231c2ae7f33ffd
Tx public key: 6c9dc8c164eae401db2487c35c3c8505fefa32b38169508210ad04659afe2dab
Timestamp: 1582054329 Timestamp [UCT]: 2020-02-18 19:32:09 Age [y:d:h:m:s]: 04:356:19:48:44
Block: 67707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147169 RingCT/type: yes/0
Extra: 016c9dc8c164eae401db2487c35c3c8505fefa32b38169508210ad04659afe2dab0211000000048a2ee0d9000000000000000000

1 output(s) for total of 366.150312832000 dcy

stealth address amount amount idx
00: eeeef1e4fe8168f4d2f1da9a199a48d972d77436cd0e2674072854dbea7de0fc 366.150312832000 124696 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": 67717, "vin": [ { "gen": { "height": 67707 } } ], "vout": [ { "amount": 366150312832, "target": { "key": "eeeef1e4fe8168f4d2f1da9a199a48d972d77436cd0e2674072854dbea7de0fc" } } ], "extra": [ 1, 108, 157, 200, 193, 100, 234, 228, 1, 219, 36, 135, 195, 92, 60, 133, 5, 254, 250, 50, 179, 129, 105, 80, 130, 16, 173, 4, 101, 154, 254, 45, 171, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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