Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 158b219f74c8d94f58a537433203e2b64a4eaf8b6ea45b2cab7a2baa75adffe2

Tx prefix hash: 79fcf0936c7cd298f88d30a173a7abf16bd1ac8ce3a4d17237da404cfa76ea7c
Tx public key: 9585da380784005952599e6d3fd41686e28e1b2f455a14736a6dcbdf28e0d697
Timestamp: 1709047713 Timestamp [UCT]: 2024-02-27 15:28:33 Age [y:d:h:m:s]: 01:116:08:58:45
Block: 966767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344019 RingCT/type: yes/0
Extra: 019585da380784005952599e6d3fd41686e28e1b2f455a14736a6dcbdf28e0d6970211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3875be264009991f4b864fcc65ed42e3ae088fc314f63feed44956a006d512cb 0.600000000000 1426538 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": 966777, "vin": [ { "gen": { "height": 966767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3875be264009991f4b864fcc65ed42e3ae088fc314f63feed44956a006d512cb" } } ], "extra": [ 1, 149, 133, 218, 56, 7, 132, 0, 89, 82, 89, 158, 109, 63, 212, 22, 134, 226, 142, 27, 47, 69, 90, 20, 115, 106, 109, 203, 223, 40, 224, 214, 151, 2, 17, 0, 0, 0, 5, 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