Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea03b2586f9810b2286eead4163d76a513c6a4502d64005cc50b645921d42f8d

Tx prefix hash: e44ed37474ebc150feb111923a3bc3038b5fd5ea0bb2fad70022961c29f8301b
Tx public key: f2db1047c625c7ea6964c6c88c9c9f9abb85ad578bb9714193ecbe23fc7eac5d
Timestamp: 1581090441 Timestamp [UCT]: 2020-02-07 15:47:21 Age [y:d:h:m:s]: 05:070:16:11:04
Block: 60640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202641 RingCT/type: yes/0
Extra: 01f2db1047c625c7ea6964c6c88c9c9f9abb85ad578bb9714193ecbe23fc7eac5d0211000000017adf42d3000000000000000000

1 output(s) for total of 386.433994796000 dcy

stealth address amount amount idx
00: 32e99849bbcaf8f1313cd310a7c8a65764c7df0e12009a52b5d7ea6837aeb603 386.433994796000 111670 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": 60650, "vin": [ { "gen": { "height": 60640 } } ], "vout": [ { "amount": 386433994796, "target": { "key": "32e99849bbcaf8f1313cd310a7c8a65764c7df0e12009a52b5d7ea6837aeb603" } } ], "extra": [ 1, 242, 219, 16, 71, 198, 37, 199, 234, 105, 100, 198, 200, 140, 156, 159, 154, 187, 133, 173, 87, 139, 185, 113, 65, 147, 236, 190, 35, 252, 126, 172, 93, 2, 17, 0, 0, 0, 1, 122, 223, 66, 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