Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d32b19b42ac559763143f85d2077c79f2780f20d32a0c83c7215f76442dc0e6

Tx prefix hash: 78b439399b38e0af72249e95c5ed5f6d35208e4e613d5cf1c5617800717df31d
Tx public key: 53fe8432f4b88dcaa01525281e975984ccba69459ff7a65a8b14e8e28ca5d729
Timestamp: 1712395371 Timestamp [UCT]: 2024-04-06 09:22:51 Age [y:d:h:m:s]: 01:002:10:10:32
Block: 994480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262706 RingCT/type: yes/0
Extra: 0153fe8432f4b88dcaa01525281e975984ccba69459ff7a65a8b14e8e28ca5d72902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f0c8a364cda08892348b3b4d6ca25674a5e24050e70fafb070f4feaca60c9a0 0.600000000000 1454882 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": 994490, "vin": [ { "gen": { "height": 994480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f0c8a364cda08892348b3b4d6ca25674a5e24050e70fafb070f4feaca60c9a0" } } ], "extra": [ 1, 83, 254, 132, 50, 244, 184, 141, 202, 160, 21, 37, 40, 30, 151, 89, 132, 204, 186, 105, 69, 159, 247, 166, 90, 139, 20, 232, 226, 140, 165, 215, 41, 2, 17, 0, 0, 0, 5, 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