Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a272162d0ff03cc9653d97b8e5766ee478884019975c298cda2dc87e919f0f1b

Tx prefix hash: 4a7e1d60a7e052122c5fe35fcab6f7a8ef0b4cd4c1880e9463f42a04b0f9b6c1
Tx public key: fc0fe2370dce1ca33d1fb67b9b5d75691956c3c906350e7f212894a38e4dbecb
Timestamp: 1721400819 Timestamp [UCT]: 2024-07-19 14:53:39 Age [y:d:h:m:s]: 00:299:20:51:46
Block: 1069180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214253 RingCT/type: yes/0
Extra: 01fc0fe2370dce1ca33d1fb67b9b5d75691956c3c906350e7f212894a38e4dbecb021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8756f2cf906231809252aa949fd361b5d6bc6ac65aaf1e2a7ec4be8a8384740 0.600000000000 1540503 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": 1069190, "vin": [ { "gen": { "height": 1069180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8756f2cf906231809252aa949fd361b5d6bc6ac65aaf1e2a7ec4be8a8384740" } } ], "extra": [ 1, 252, 15, 226, 55, 13, 206, 28, 163, 61, 31, 182, 123, 155, 93, 117, 105, 25, 86, 195, 201, 6, 53, 14, 127, 33, 40, 148, 163, 142, 77, 190, 203, 2, 17, 0, 0, 0, 6, 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