Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b08c1c4203bef03a2929d92729970c9b960f0cee8d8a8abb7e5b3736a0cda78

Tx prefix hash: adde7cdf549defb807669fa721102135a8318d37216a03dabbf0723d3089b4ef
Tx public key: ba86397a4e5e3a26862544c210bb5d21e995a0d30b4495b8adc55cc1e1bbda06
Timestamp: 1756655175 Timestamp [UCT]: 2025-08-31 15:46:15 Age [y:d:h:m:s]: 00:113:20:26:05
Block: 1358472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81378 RingCT/type: yes/0
Extra: 01ba86397a4e5e3a26862544c210bb5d21e995a0d30b4495b8adc55cc1e1bbda06021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44814f0b03741d971a87ddf68e56e0cab4ac9351b45bd8e1354a937ee4e8f4f2 0.600000000000 1846485 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": 1358482, "vin": [ { "gen": { "height": 1358472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44814f0b03741d971a87ddf68e56e0cab4ac9351b45bd8e1354a937ee4e8f4f2" } } ], "extra": [ 1, 186, 134, 57, 122, 78, 94, 58, 38, 134, 37, 68, 194, 16, 187, 93, 33, 233, 149, 160, 211, 11, 68, 149, 184, 173, 197, 92, 193, 225, 187, 218, 6, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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