Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a120140d95c40bb971d5d2dbf623cfa7b4e6bd7a89ee0592eff5cb99e54f5add

Tx prefix hash: e304cc947650527cf012684455638ba02a0bb1cd986c317cbee4f24753c4e88d
Tx public key: 0c3d9f85fd8aa8d7bd4b591b5509f16f8751222cff21242a19589d743cebfc02
Timestamp: 1761763632 Timestamp [UCT]: 2025-10-29 18:47:12 Age [y:d:h:m:s]: 00:022:03:03:06
Block: 1400681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15831 RingCT/type: yes/0
Extra: 010c3d9f85fd8aa8d7bd4b591b5509f16f8751222cff21242a19589d743cebfc0202110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0d257341845e7d32c527516ff51cd2339584c394f0d59153459f952b5ab1013 0.600000000000 1888998 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": 1400691, "vin": [ { "gen": { "height": 1400681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0d257341845e7d32c527516ff51cd2339584c394f0d59153459f952b5ab1013" } } ], "extra": [ 1, 12, 61, 159, 133, 253, 138, 168, 215, 189, 75, 89, 27, 85, 9, 241, 111, 135, 81, 34, 44, 255, 33, 36, 42, 25, 88, 157, 116, 60, 235, 252, 2, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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