Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6a3cf9364bcf3e5cec8f5f7323d32ddd292d6302df809c93af4eaa32c4de27c

Tx prefix hash: d80cc6e5fc7c1bf456e180a07b4dcdf0e9b673aee637d1900a3d01597021c067
Tx public key: fd16a41b9163a52c6a582ed614dcbbb5e1507df465867f92437967d1bcf90389
Timestamp: 1723273029 Timestamp [UCT]: 2024-08-10 06:57:09 Age [y:d:h:m:s]: 00:259:07:04:06
Block: 1084690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185221 RingCT/type: yes/0
Extra: 01fd16a41b9163a52c6a582ed614dcbbb5e1507df465867f92437967d1bcf90389021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 437d98869b0fd6621e6a0ad146fa7e9c670be84dab59d1512ef84db895543480 0.600000000000 1559057 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": 1084700, "vin": [ { "gen": { "height": 1084690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "437d98869b0fd6621e6a0ad146fa7e9c670be84dab59d1512ef84db895543480" } } ], "extra": [ 1, 253, 22, 164, 27, 145, 99, 165, 44, 106, 88, 46, 214, 20, 220, 187, 181, 225, 80, 125, 244, 101, 134, 127, 146, 67, 121, 103, 209, 188, 249, 3, 137, 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