Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ec1e521ebab5e5cbb13c5344724f4a5b52e4e26107c7d4a92c08eb82bc0f7ef

Tx prefix hash: 209b35de7b0b43d577ca50a289c9c07f6c9089479fe5fd4c991cdaf4e5241d6c
Tx public key: e0e5a938b9894ba490679d6dd64a682f47d331421dd6d22b0c60e340bdbf7ed6
Timestamp: 1759089897 Timestamp [UCT]: 2025-09-28 20:04:57 Age [y:d:h:m:s]: 00:009:08:52:20
Block: 1378501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6714 RingCT/type: yes/0
Extra: 01e0e5a938b9894ba490679d6dd64a682f47d331421dd6d22b0c60e340bdbf7ed602110000000697baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 040b72083428a408ed8c865f800241f64c5240bb37f9f5b28c5deee3b06d86a5 0.600000000000 1866596 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": 1378511, "vin": [ { "gen": { "height": 1378501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "040b72083428a408ed8c865f800241f64c5240bb37f9f5b28c5deee3b06d86a5" } } ], "extra": [ 1, 224, 229, 169, 56, 185, 137, 75, 164, 144, 103, 157, 109, 214, 74, 104, 47, 71, 211, 49, 66, 29, 214, 210, 43, 12, 96, 227, 64, 189, 191, 126, 214, 2, 17, 0, 0, 0, 6, 151, 186, 249, 34, 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