Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a961640afc1ac5b1ec41b783af2004a114fd2cb2d633d9ca0e31e517da0a436e

Tx prefix hash: 230d34108c20399ffc2d1a8a67a107c5a6d80735581a9d4b5d0d31fd9d0c552a
Tx public key: 7e534ac5d9dc7a76c18f59b2f813bf5130ebd112b0082c56d8c3da42886d02eb
Timestamp: 1708347291 Timestamp [UCT]: 2024-02-19 12:54:51 Age [y:d:h:m:s]: 01:046:12:55:57
Block: 960949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294285 RingCT/type: yes/0
Extra: 017e534ac5d9dc7a76c18f59b2f813bf5130ebd112b0082c56d8c3da42886d02eb02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42095f7566f266337e9bf82c47b2e30a9f376db2a648bf6c482d38bdac89eaa3 0.600000000000 1420536 of 15

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": 960959, "vin": [ { "gen": { "height": 960949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42095f7566f266337e9bf82c47b2e30a9f376db2a648bf6c482d38bdac89eaa3" } } ], "extra": [ 1, 126, 83, 74, 197, 217, 220, 122, 118, 193, 143, 89, 178, 248, 19, 191, 81, 48, 235, 209, 18, 176, 8, 44, 86, 216, 195, 218, 66, 136, 109, 2, 235, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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