Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6060a032f1e42f5bd00a7988b008ab0d93042959979eb0874ebfe2a04e9b1d3e

Tx prefix hash: e2cc6d0c89f9d44a9249465e2719efbabde403a20b88702a026b01a117f5325f
Tx public key: 97d334b3824786d204f4320281c16a5e68d34f2ed89d894c3663cee6a32b4a6e
Timestamp: 1709654538 Timestamp [UCT]: 2024-03-05 16:02:18 Age [y:d:h:m:s]: 01:255:12:28:47
Block: 971791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441348 RingCT/type: yes/0
Extra: 0197d334b3824786d204f4320281c16a5e68d34f2ed89d894c3663cee6a32b4a6e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db60baf21e2423b2d7fc252ddfe78b3df0667bb597512f9439a61bcc53c455ae 0.600000000000 1431694 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": 971801, "vin": [ { "gen": { "height": 971791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db60baf21e2423b2d7fc252ddfe78b3df0667bb597512f9439a61bcc53c455ae" } } ], "extra": [ 1, 151, 211, 52, 179, 130, 71, 134, 210, 4, 244, 50, 2, 129, 193, 106, 94, 104, 211, 79, 46, 216, 157, 137, 76, 54, 99, 206, 230, 163, 43, 74, 110, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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