Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32b1aa4251b45a902ba0ec6c0259042fd1c2e9f185bb250fae72ec8385735740

Tx prefix hash: 8af10894f17f12fe2ab6632bd692b46f486e95e13d51df4c3674767a834ff9bb
Tx public key: 3e69a6867825a68b8f17a0db4ea9141c7de7accaca08c19f134d07decd0ed2f3
Timestamp: 1709082355 Timestamp [UCT]: 2024-02-28 01:05:55 Age [y:d:h:m:s]: 01:260:12:13:04
Block: 967055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444915 RingCT/type: yes/0
Extra: 013e69a6867825a68b8f17a0db4ea9141c7de7accaca08c19f134d07decd0ed2f302110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 179a6f99b68b71a896fa5689358075d7276fb1d284cc9afff1472f9fa9dc15cd 0.600000000000 1426826 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": 967065, "vin": [ { "gen": { "height": 967055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "179a6f99b68b71a896fa5689358075d7276fb1d284cc9afff1472f9fa9dc15cd" } } ], "extra": [ 1, 62, 105, 166, 134, 120, 37, 166, 139, 143, 23, 160, 219, 78, 169, 20, 28, 125, 231, 172, 202, 202, 8, 193, 159, 19, 77, 7, 222, 205, 14, 210, 243, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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