Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeacad9f212dcfdddfa1541df3e7baeb79cbab36081f0bccd03c9c86765f49aa

Tx prefix hash: 6a50d1f9ce2bf296edf61e026940f95c945953140095e173e6987916e924bd9b
Tx public key: f8d9fa9ad16d22004f8ba5430cd1621ef3af80b98c471a42e6f5c60fbc24743c
Timestamp: 1729431060 Timestamp [UCT]: 2024-10-20 13:31:00 Age [y:d:h:m:s]: 00:179:13:28:52
Block: 1135728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128123 RingCT/type: yes/0
Extra: 01f8d9fa9ad16d22004f8ba5430cd1621ef3af80b98c471a42e6f5c60fbc24743c0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddc247d2a8b68fcc9012c7c14c9793611de81ec96b076f8b0941f20ae2b42c5d 0.600000000000 1619067 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": 1135738, "vin": [ { "gen": { "height": 1135728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddc247d2a8b68fcc9012c7c14c9793611de81ec96b076f8b0941f20ae2b42c5d" } } ], "extra": [ 1, 248, 217, 250, 154, 209, 109, 34, 0, 79, 139, 165, 67, 12, 209, 98, 30, 243, 175, 128, 185, 140, 71, 26, 66, 230, 245, 198, 15, 188, 36, 116, 60, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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