Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 204a32dab5ca5b90b8a2bd44dbb3ab9f960e5ebf3edd658a4ba0b1dc09237384

Tx prefix hash: dd065c2c78903e8cd6ab5575c202d8f343b5686a1da1282f5a8a95223d5ae122
Tx public key: 8c21cbbc170dc8102d5139a5c8e5fdb71497480beb342f3dea20cc74d41ef61a
Timestamp: 1748177506 Timestamp [UCT]: 2025-05-25 12:51:46 Age [y:d:h:m:s]: 00:178:19:09:43
Block: 1290630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125477 RingCT/type: yes/0
Extra: 018c21cbbc170dc8102d5139a5c8e5fdb71497480beb342f3dea20cc74d41ef61a0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f214fe82fa0b9a6db21860bd0012dcbb6eee0009cd87e0cb7bc35d6043fed45 0.600000000000 1778099 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": 1290640, "vin": [ { "gen": { "height": 1290630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f214fe82fa0b9a6db21860bd0012dcbb6eee0009cd87e0cb7bc35d6043fed45" } } ], "extra": [ 1, 140, 33, 203, 188, 23, 13, 200, 16, 45, 81, 57, 165, 200, 229, 253, 183, 20, 151, 72, 11, 235, 52, 47, 61, 234, 32, 204, 116, 212, 30, 246, 26, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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