Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2606a41e0a35414b6e450b7c1a749fa0915201ef4b26604ccbd75505fc5556

Tx prefix hash: 1ac1ed03ecd53e52e4530b90c39fd2d45aacc804574c1e703d19d4e81fefbdd3
Tx public key: 7a06afe41706c9d79689eefdb50eec5c6ddbd7df828da23eb0f4294dc9094ce4
Timestamp: 1700612186 Timestamp [UCT]: 2023-11-22 00:16:26 Age [y:d:h:m:s]: 01:093:16:03:40
Block: 896824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328067 RingCT/type: yes/0
Extra: 017a06afe41706c9d79689eefdb50eec5c6ddbd7df828da23eb0f4294dc9094ce40211000000054b8f5122000000000000000000

1 output(s) for total of 0.655314514000 dcy

stealth address amount amount idx
00: 37fc7cf79885dbdbc2cc78d291d9239250d472bf71e1dd29fc586b0f1178bc81 0.655314514000 1353167 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": 896834, "vin": [ { "gen": { "height": 896824 } } ], "vout": [ { "amount": 655314514, "target": { "key": "37fc7cf79885dbdbc2cc78d291d9239250d472bf71e1dd29fc586b0f1178bc81" } } ], "extra": [ 1, 122, 6, 175, 228, 23, 6, 201, 215, 150, 137, 238, 253, 181, 14, 236, 92, 109, 219, 215, 223, 130, 141, 162, 62, 176, 244, 41, 77, 201, 9, 76, 228, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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