Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e79be2bfcced9d282f0660364ae9eb609b99e83b3b3f7416d9dc18fbf8e33640

Tx prefix hash: 71de8eebac27adca2a54e7e49215374df596e0728d0eeaa65634454ef0eb1609
Tx public key: e94b3b6f4cc8f6e3f947edb6caf45c8b7901754d897ac547b9677950921bcc4f
Timestamp: 1761069141 Timestamp [UCT]: 2025-10-21 17:52:21 Age [y:d:h:m:s]: 00:075:07:41:19
Block: 1394933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53924 RingCT/type: yes/0
Extra: 01e94b3b6f4cc8f6e3f947edb6caf45c8b7901754d897ac547b9677950921bcc4f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8659b1c0b645b17c9daac8c2ae62dc93e30a449fbe71db2875576605efed1fe0 0.600000000000 1883208 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": 1394943, "vin": [ { "gen": { "height": 1394933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8659b1c0b645b17c9daac8c2ae62dc93e30a449fbe71db2875576605efed1fe0" } } ], "extra": [ 1, 233, 75, 59, 111, 76, 200, 246, 227, 249, 71, 237, 182, 202, 244, 92, 139, 121, 1, 117, 77, 137, 122, 197, 71, 185, 103, 121, 80, 146, 27, 204, 79, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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