Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e3990355450ecc9b19c003593cb1018e3cdfe216389120862b960206b084a1f

Tx prefix hash: e9d55d212ccd101b2df2600f1c6266d10eb79def5f2acebab576a55905c2216b
Tx public key: 703c959fd9a917e7bb9d4c51a34070c0eeea98dd501b32cf987f522f0db4fc57
Timestamp: 1720477782 Timestamp [UCT]: 2024-07-08 22:29:42 Age [y:d:h:m:s]: 00:184:07:10:22
Block: 1061523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131873 RingCT/type: yes/0
Extra: 01703c959fd9a917e7bb9d4c51a34070c0eeea98dd501b32cf987f522f0db4fc57021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01433f54b1a924f081abe106d80535640dfba05c1776cb6d3e1530ff3c917ced 0.600000000000 1532014 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": 1061533, "vin": [ { "gen": { "height": 1061523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01433f54b1a924f081abe106d80535640dfba05c1776cb6d3e1530ff3c917ced" } } ], "extra": [ 1, 112, 60, 149, 159, 217, 169, 23, 231, 187, 157, 76, 81, 163, 64, 112, 192, 238, 234, 152, 221, 80, 27, 50, 207, 152, 127, 82, 47, 13, 180, 252, 87, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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