Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9854e831366900ee27d965729ae08ba118b45765fb7a3cd118d940a866807e7f

Tx prefix hash: 5e0af82c1b521a94cc47819f126e6ae9191acf096f2cb6e2d10cd4e4e243c620
Tx public key: 0e05e988f2a2318e1368673f26ff99e68e67f940ed1f7460d15c30b96ef77761
Timestamp: 1726275759 Timestamp [UCT]: 2024-09-14 01:02:39 Age [y:d:h:m:s]: 00:208:23:14:28
Block: 1109582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149184 RingCT/type: yes/0
Extra: 010e05e988f2a2318e1368673f26ff99e68e67f940ed1f7460d15c30b96ef7776102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f546d080723b1095a15d49b363096d903c0e437d60162262c2f4ee42437e0f8 0.600000000000 1587885 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": 1109592, "vin": [ { "gen": { "height": 1109582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f546d080723b1095a15d49b363096d903c0e437d60162262c2f4ee42437e0f8" } } ], "extra": [ 1, 14, 5, 233, 136, 242, 162, 49, 142, 19, 104, 103, 63, 38, 255, 153, 230, 142, 103, 249, 64, 237, 31, 116, 96, 209, 92, 48, 185, 110, 247, 119, 97, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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