Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19491ab66d9853fbab0116c454c18ec7e89d1177cf72c391d51fb43efb8af032

Tx prefix hash: 2ba5f4cd13ebbb0fe085117784f3959edbdaff894e70de36b284f58ff3fa1836
Tx public key: d319f3c5daa7286725f932f482d16ef5257ad31558c3248b89beb0a0f54766a3
Timestamp: 1582730159 Timestamp [UCT]: 2020-02-26 15:15:59 Age [y:d:h:m:s]: 04:264:20:07:59
Block: 72431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1082506 RingCT/type: yes/0
Extra: 01d319f3c5daa7286725f932f482d16ef5257ad31558c3248b89beb0a0f54766a302110000002a8a2ee0d9000000000000000000

1 output(s) for total of 353.200913884000 dcy

stealth address amount amount idx
00: 6a9c255f9acabeef892c4a5beb7556f06fe7baf8c636813fc8199b51307071e6 353.200913884000 133793 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": 72441, "vin": [ { "gen": { "height": 72431 } } ], "vout": [ { "amount": 353200913884, "target": { "key": "6a9c255f9acabeef892c4a5beb7556f06fe7baf8c636813fc8199b51307071e6" } } ], "extra": [ 1, 211, 25, 243, 197, 218, 167, 40, 103, 37, 249, 50, 244, 130, 209, 110, 245, 37, 122, 211, 21, 88, 195, 36, 139, 137, 190, 176, 160, 245, 71, 102, 163, 2, 17, 0, 0, 0, 42, 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