Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a27b517841302c3a305f065d6ebd9261cc517cd2e7fa2d8858e7326ed7bc9bc

Tx prefix hash: 0d757a9b2ba872f30360af290d305a84b4f092069487937a4a3aabd5b3c47329
Tx public key: 4eae02aa39ccdfd491c2380e45d811ad31a8830782e2c74f10ad2cd3ceb8a75e
Timestamp: 1761121914 Timestamp [UCT]: 2025-10-22 08:31:54 Age [y:d:h:m:s]: 00:070:12:16:26
Block: 1395363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50480 RingCT/type: yes/0
Extra: 014eae02aa39ccdfd491c2380e45d811ad31a8830782e2c74f10ad2cd3ceb8a75e0211000000085dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e92aff141522db8922eabe570ade80313a8cf6650c963a4088a9dba3f8c89e9 0.600000000000 1883640 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": 1395373, "vin": [ { "gen": { "height": 1395363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e92aff141522db8922eabe570ade80313a8cf6650c963a4088a9dba3f8c89e9" } } ], "extra": [ 1, 78, 174, 2, 170, 57, 204, 223, 212, 145, 194, 56, 14, 69, 216, 17, 173, 49, 168, 131, 7, 130, 226, 199, 79, 16, 173, 44, 211, 206, 184, 167, 94, 2, 17, 0, 0, 0, 8, 93, 251, 190, 42, 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