Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b1301c752112cf7f93f67f3fe7d86776539c263f475d17a6308eb0a5edf5e9

Tx prefix hash: 77ac0db20c4e33122732cf7adf996c6621975bff721ad6a6ca21c0bda5d09663
Tx public key: 3b4c3ba1f42f9a9c9048213bc03503a32fe113f8cc89999c4a4aa3acd3975f9b
Timestamp: 1582402474 Timestamp [UCT]: 2020-02-22 20:14:34 Age [y:d:h:m:s]: 04:310:05:01:42
Block: 70420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114241 RingCT/type: yes/0
Extra: 013b4c3ba1f42f9a9c9048213bc03503a32fe113f8cc89999c4a4aa3acd3975f9b0211000000044943cd9f000000000000000000

1 output(s) for total of 358.659391412000 dcy

stealth address amount amount idx
00: 70753ee2208d610a017ba97061bc1aeb5e4dfd6213e449e90eb980a95709c7d7 358.659391412000 130115 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": 70430, "vin": [ { "gen": { "height": 70420 } } ], "vout": [ { "amount": 358659391412, "target": { "key": "70753ee2208d610a017ba97061bc1aeb5e4dfd6213e449e90eb980a95709c7d7" } } ], "extra": [ 1, 59, 76, 59, 161, 244, 47, 154, 156, 144, 72, 33, 59, 192, 53, 3, 163, 47, 225, 19, 248, 204, 137, 153, 156, 74, 74, 163, 172, 211, 151, 95, 155, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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