Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40dea093bcb374cdb9c012ab3d0ec25bf1d76c239dbf61ca5aa60042f9ab8dc0

Tx prefix hash: cce203a9ab1728421b92188bf33bf81ee5dc606c2d4d967b41b6ea01e889d9f1
Tx public key: 0b15d0c4fb957f20eec7b64e87f3d4e39d971b9cf791924fc40fc5dd9cc6b89e
Timestamp: 1686948947 Timestamp [UCT]: 2023-06-16 20:55:47 Age [y:d:h:m:s]: 01:215:22:56:42
Block: 783788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415749 RingCT/type: yes/0
Extra: 010b15d0c4fb957f20eec7b64e87f3d4e39d971b9cf791924fc40fc5dd9cc6b89e021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.552333907000 dcy

stealth address amount amount idx
00: e17369a1ace714a9dfd87a0ecc8e94de735cf7beed943611ce3f60a523f440af 1.552333907000 1233657 of 0

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": 783798, "vin": [ { "gen": { "height": 783788 } } ], "vout": [ { "amount": 1552333907, "target": { "key": "e17369a1ace714a9dfd87a0ecc8e94de735cf7beed943611ce3f60a523f440af" } } ], "extra": [ 1, 11, 21, 208, 196, 251, 149, 127, 32, 238, 199, 182, 78, 135, 243, 212, 227, 157, 151, 27, 156, 247, 145, 146, 79, 196, 15, 197, 221, 156, 198, 184, 158, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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