Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8246d6d001e121b4fc89ef624a79326b3a7b25cffea19b2e47b9f3bda7ab913a

Tx prefix hash: 51d898bb4da38449575eb7dd248458d5ad32c25514656f2d8639f979be1d5e0c
Tx public key: 0624b4f3ad1b65082526596da8070efb089a9f3b9adb084efd5e68bdf389a201
Timestamp: 1705340019 Timestamp [UCT]: 2024-01-15 17:33:39 Age [y:d:h:m:s]: 01:322:04:08:08
Block: 935997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489114 RingCT/type: yes/0
Extra: 010624b4f3ad1b65082526596da8070efb089a9f3b9adb084efd5e68bdf389a2010211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e583e1e89362014cb1aca8e468c47f7c4dd08ed18c7e3cb05f4b443496c57ef8 0.600000000000 1394019 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": 936007, "vin": [ { "gen": { "height": 935997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e583e1e89362014cb1aca8e468c47f7c4dd08ed18c7e3cb05f4b443496c57ef8" } } ], "extra": [ 1, 6, 36, 180, 243, 173, 27, 101, 8, 37, 38, 89, 109, 168, 7, 14, 251, 8, 154, 159, 59, 154, 219, 8, 78, 253, 94, 104, 189, 243, 137, 162, 1, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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