Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeab5808a34523420b36ff1e5a12a3a41b3933dc05b42a02dac45c943e63246e

Tx prefix hash: 040513f845831c2462ea8d4661c7072e5068e4adbda8bb21cd7e4748d34b3722
Tx public key: 6ce77170928affcd927a09302f3ba618d3a6313e47c0b3a965861aa4f9710d18
Timestamp: 1712530048 Timestamp [UCT]: 2024-04-07 22:47:28 Age [y:d:h:m:s]: 01:039:08:22:35
Block: 995599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289130 RingCT/type: yes/0
Extra: 016ce77170928affcd927a09302f3ba618d3a6313e47c0b3a965861aa4f9710d180211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60fe98f389bea5af5f814b138040b53acebdbdbaa3b2aa0df528faed21ef9987 0.600000000000 1456009 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": 995609, "vin": [ { "gen": { "height": 995599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60fe98f389bea5af5f814b138040b53acebdbdbaa3b2aa0df528faed21ef9987" } } ], "extra": [ 1, 108, 231, 113, 112, 146, 138, 255, 205, 146, 122, 9, 48, 47, 59, 166, 24, 211, 166, 49, 62, 71, 192, 179, 169, 101, 134, 26, 164, 249, 113, 13, 24, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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