Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93d893300e48f972c5f742ad33a37f379fceb8ee3c02e6139963a61ddd98be1e

Tx prefix hash: 50092809c57bbe249b7f4127f20328b7ac9419bc63e86b3f70a3caea182f1097
Tx public key: 026ab5dd0aea3480088f5f8a203268aa529b7f4810ba1bb1be8131a7b368b924
Timestamp: 1749653052 Timestamp [UCT]: 2025-06-11 14:44:12 Age [y:d:h:m:s]: 00:152:08:38:26
Block: 1302830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106573 RingCT/type: yes/0
Extra: 01026ab5dd0aea3480088f5f8a203268aa529b7f4810ba1bb1be8131a7b368b92402110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e733f05454df385d1af2cead89fd0169463d8f51e7402769f43e3bec219b0a5e 0.600000000000 1790403 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": 1302840, "vin": [ { "gen": { "height": 1302830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e733f05454df385d1af2cead89fd0169463d8f51e7402769f43e3bec219b0a5e" } } ], "extra": [ 1, 2, 106, 181, 221, 10, 234, 52, 128, 8, 143, 95, 138, 32, 50, 104, 170, 82, 155, 127, 72, 16, 186, 27, 177, 190, 129, 49, 167, 179, 104, 185, 36, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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