Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e93567eae8cf45bf6a82771280f2bed498739727742e4d105bf856695f098d6d

Tx prefix hash: 1ec8e9bdbb22773f4d3944fd80a7d99f8befa9037b46aef5c47278db9d1bc282
Tx public key: a25005fb58969ea0e5a2ee636450ee3b3c6e43ae22c205faa021eb83c0b561ea
Timestamp: 1723935905 Timestamp [UCT]: 2024-08-17 23:05:05 Age [y:d:h:m:s]: 00:227:04:05:02
Block: 1090191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162211 RingCT/type: yes/0
Extra: 01a25005fb58969ea0e5a2ee636450ee3b3c6e43ae22c205faa021eb83c0b561ea021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5566c0a4c3745db6854161a35bddc41dd4bf23656b40aaf4c4c2080e317f050d 0.600000000000 1564814 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": 1090201, "vin": [ { "gen": { "height": 1090191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5566c0a4c3745db6854161a35bddc41dd4bf23656b40aaf4c4c2080e317f050d" } } ], "extra": [ 1, 162, 80, 5, 251, 88, 150, 158, 160, 229, 162, 238, 99, 100, 80, 238, 59, 60, 110, 67, 174, 34, 194, 5, 250, 160, 33, 235, 131, 192, 181, 97, 234, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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