Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa68431929b4d2d3dbac460e34886376ef1debe4b537573df49f15304ef6067c

Tx prefix hash: 7b7c548d1b956d01d52299168878dfbcb73c1fbc74762c958b2f2b9cb08be712
Tx public key: b9201ecd54b05b176152c94351321728f3cfd4febe0dbaa176728c0f087a8af0
Timestamp: 1726719182 Timestamp [UCT]: 2024-09-19 04:13:02 Age [y:d:h:m:s]: 00:196:20:22:44
Block: 1113262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140511 RingCT/type: yes/0
Extra: 01b9201ecd54b05b176152c94351321728f3cfd4febe0dbaa176728c0f087a8af0021100000002bdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea64766f5d101b9ae8e200de5ee29841df3a12b4cda6b09d1e7fc9c209e7e24b 0.600000000000 1592871 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": 1113272, "vin": [ { "gen": { "height": 1113262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea64766f5d101b9ae8e200de5ee29841df3a12b4cda6b09d1e7fc9c209e7e24b" } } ], "extra": [ 1, 185, 32, 30, 205, 84, 176, 91, 23, 97, 82, 201, 67, 81, 50, 23, 40, 243, 207, 212, 254, 190, 13, 186, 161, 118, 114, 140, 15, 8, 122, 138, 240, 2, 17, 0, 0, 0, 2, 189, 175, 233, 204, 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