Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960a854d4d5e66ca39b91023067cf355f24b99d57d4943c0fc5f3c83e2153f5e

Tx prefix hash: 0a0c690562a5f543c052390c2773e4d922a9f080cffe9451a9338cb7992e7372
Tx public key: c0b5a8120f22a24cdff29e95128c69a2f765ba5a43f2fc34b8455e695e8be8c1
Timestamp: 1736700812 Timestamp [UCT]: 2025-01-12 16:53:32 Age [y:d:h:m:s]: 00:157:17:38:27
Block: 1195876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112417 RingCT/type: yes/0
Extra: 01c0b5a8120f22a24cdff29e95128c69a2f765ba5a43f2fc34b8455e695e8be8c10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d39dc6ce9704a0f289090095d55aaca25e9950180e744481624bb4ff52c39378 0.600000000000 1682469 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": 1195886, "vin": [ { "gen": { "height": 1195876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d39dc6ce9704a0f289090095d55aaca25e9950180e744481624bb4ff52c39378" } } ], "extra": [ 1, 192, 181, 168, 18, 15, 34, 162, 76, 223, 242, 158, 149, 18, 140, 105, 162, 247, 101, 186, 90, 67, 242, 252, 52, 184, 69, 94, 105, 94, 139, 232, 193, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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