Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 993d2f491c90afe842f1a41ee84e5cba45ca24bad9a2ff6592435382e6bf05bf

Tx prefix hash: bf6bf64954171fdab6bd62de9688e974c0f05c7701d14ea5e4c8d096286cc660
Tx public key: f13d64ce62e7708f659619167853f7dd1d0a2b6c7ed69994015a61051653e3f2
Timestamp: 1725592098 Timestamp [UCT]: 2024-09-06 03:08:18 Age [y:d:h:m:s]: 00:265:00:26:09
Block: 1103916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189300 RingCT/type: yes/0
Extra: 01f13d64ce62e7708f659619167853f7dd1d0a2b6c7ed69994015a61051653e3f2021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3b01a58983528fcc9f8b4bdca3358ae1c711085fed0d364b8a078e4a3a612a3 0.600000000000 1580931 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": 1103926, "vin": [ { "gen": { "height": 1103916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3b01a58983528fcc9f8b4bdca3358ae1c711085fed0d364b8a078e4a3a612a3" } } ], "extra": [ 1, 241, 61, 100, 206, 98, 231, 112, 143, 101, 150, 25, 22, 120, 83, 247, 221, 29, 10, 43, 108, 126, 214, 153, 148, 1, 90, 97, 5, 22, 83, 227, 242, 2, 17, 0, 0, 0, 6, 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