Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8e30ae103d1f57990329aa9e835c21ca219c322480eb6b9303862ec9cd74166

Tx prefix hash: 4b49805ead9017e0c7d5038b08cb779e070f2204dc68da29ba9e87d726db63eb
Tx public key: cd2dc2d0b8116705efc48a193ef336a5507caee5732d8fc7777c9ff856c3ea05
Timestamp: 1748009246 Timestamp [UCT]: 2025-05-23 14:07:26 Age [y:d:h:m:s]: 00:251:20:36:43
Block: 1289228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177615 RingCT/type: yes/0
Extra: 01cd2dc2d0b8116705efc48a193ef336a5507caee5732d8fc7777c9ff856c3ea050211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a34d5b068c47c25a775aa658330e24a87b0878a0e0a557ad870a248f6fca03ae 0.600000000000 1776695 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": 1289238, "vin": [ { "gen": { "height": 1289228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a34d5b068c47c25a775aa658330e24a87b0878a0e0a557ad870a248f6fca03ae" } } ], "extra": [ 1, 205, 45, 194, 208, 184, 17, 103, 5, 239, 196, 138, 25, 62, 243, 54, 165, 80, 124, 174, 229, 115, 45, 143, 199, 119, 124, 159, 248, 86, 195, 234, 5, 2, 17, 0, 0, 0, 5, 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