Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adea590703fa688f0c2da731f4bed0c1a0f9ca99dd4e49f5a41cf6be71caae3c

Tx prefix hash: dff10104e42e4fda9f3f6e3ef166fe87ae26706709b9d660c0155e0c20d3e8de
Tx public key: d7dbcbbd4bef27e95a8578e88bbad06aa6e583355b671bb537160cd0acb12dd1
Timestamp: 1764122578 Timestamp [UCT]: 2025-11-26 02:02:58 Age [y:d:h:m:s]: 00:001:08:01:43
Block: 1420224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 957 RingCT/type: yes/0
Extra: 01d7dbcbbd4bef27e95a8578e88bbad06aa6e583355b671bb537160cd0acb12dd1021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a56cb68625418acfcaeecd566dd7b52f807f6ed3add378acca577c87276ec0fe 0.600000000000 1908765 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": 1420234, "vin": [ { "gen": { "height": 1420224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a56cb68625418acfcaeecd566dd7b52f807f6ed3add378acca577c87276ec0fe" } } ], "extra": [ 1, 215, 219, 203, 189, 75, 239, 39, 233, 90, 133, 120, 232, 139, 186, 208, 106, 166, 229, 131, 53, 91, 103, 27, 181, 55, 22, 12, 208, 172, 177, 45, 209, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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