Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d20e5150af207aa98b961075b547803f91324f8e74562ca193727f85b528267

Tx prefix hash: f64a4dbeb67413ab80d31131d741593966d4a98f0fbbd75ee0456f6353aeb273
Tx public key: d96b0f1bf3be789ad9567c3e87aacd952d43b9a39c40240f4c9dec2bcd695209
Timestamp: 1704229779 Timestamp [UCT]: 2024-01-02 21:09:39 Age [y:d:h:m:s]: 01:022:03:22:03
Block: 926808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277118 RingCT/type: yes/0
Extra: 01d96b0f1bf3be789ad9567c3e87aacd952d43b9a39c40240f4c9dec2bcd69520902110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ffd3cd33c8800d0161ae3fbdfedb915afc2a5940f53ea19787f42a5588279f7 0.600000000000 1384606 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": 926818, "vin": [ { "gen": { "height": 926808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ffd3cd33c8800d0161ae3fbdfedb915afc2a5940f53ea19787f42a5588279f7" } } ], "extra": [ 1, 217, 107, 15, 27, 243, 190, 120, 154, 217, 86, 124, 62, 135, 170, 205, 149, 45, 67, 185, 163, 156, 64, 36, 15, 76, 157, 236, 43, 205, 105, 82, 9, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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