Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0861063a62e04a42185973a015fa132a2951d9a6d4da784a9f2e2daec7728ea0

Tx prefix hash: 3c76ddf6ef18a62bf29bb0e3ca18e7b91cbf07e54436691e4e7ae8297b07c9af
Tx public key: d4ac9acc4b855e082665866d574e1bf3b38551c4c87e3dd8fbcd8d6ddc2513f4
Timestamp: 1702014928 Timestamp [UCT]: 2023-12-08 05:55:28 Age [y:d:h:m:s]: 01:100:06:17:55
Block: 908449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332815 RingCT/type: yes/0
Extra: 01d4ac9acc4b855e082665866d574e1bf3b38551c4c87e3dd8fbcd8d6ddc2513f4021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 401cb003645fcfb8a0edda4e0d1f3ba8343ddff044757f95174ae1952cea19ad 0.600000000000 1365482 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": 908459, "vin": [ { "gen": { "height": 908449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "401cb003645fcfb8a0edda4e0d1f3ba8343ddff044757f95174ae1952cea19ad" } } ], "extra": [ 1, 212, 172, 154, 204, 75, 133, 94, 8, 38, 101, 134, 109, 87, 78, 27, 243, 179, 133, 81, 196, 200, 126, 61, 216, 251, 205, 141, 109, 220, 37, 19, 244, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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