Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efbbdb078c79c8c50afa327f80f7dec966282f201f94f79b523ffe9936d911bb

Tx prefix hash: 46cc06fbec6c9229fd12cf345af55199d53de62ba2053fe578b1b8fe0a796f1d
Tx public key: 02646be58b2de62a7cb3b1211e8916c5c593f0418a6078a86ed065b54620714b
Timestamp: 1583537053 Timestamp [UCT]: 2020-03-06 23:24:13 Age [y:d:h:m:s]: 05:043:07:58:03
Block: 77778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186211 RingCT/type: yes/0
Extra: 0102646be58b2de62a7cb3b1211e8916c5c593f0418a6078a86ed065b54620714b0211000000084ac5aa02000000000000000000

1 output(s) for total of 339.070488544000 dcy

stealth address amount amount idx
00: 8e0fdee6e95d9193612e308a26293f23f3673a08aebf648f1560bbe5bfa6f596 339.070488544000 142979 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": 77788, "vin": [ { "gen": { "height": 77778 } } ], "vout": [ { "amount": 339070488544, "target": { "key": "8e0fdee6e95d9193612e308a26293f23f3673a08aebf648f1560bbe5bfa6f596" } } ], "extra": [ 1, 2, 100, 107, 229, 139, 45, 230, 42, 124, 179, 177, 33, 30, 137, 22, 197, 197, 147, 240, 65, 138, 96, 120, 168, 110, 208, 101, 181, 70, 32, 113, 75, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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