Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20977055aa809a1dba0c1ea3a8f17e253b089d542424200a2890df0e5c0897bb

Tx prefix hash: aa108f3cabcd48b9c240b2be08c8d03de7f9b3d8715ae6bb903234eeea7913d3
Tx public key: e6e37b1d45b611e0f81c0fa86ea49540ca04a3b45b11a84af3f4af8418d1ad6e
Timestamp: 1751113717 Timestamp [UCT]: 2025-06-28 12:28:37 Age [y:d:h:m:s]: 00:144:01:46:14
Block: 1314516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101055 RingCT/type: yes/0
Extra: 01e6e37b1d45b611e0f81c0fa86ea49540ca04a3b45b11a84af3f4af8418d1ad6e02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9244aa3c87d1e343c183baa9a1532ee93adf794c91222ed7559f174f3cc74c5c 0.600000000000 1802163 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": 1314526, "vin": [ { "gen": { "height": 1314516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9244aa3c87d1e343c183baa9a1532ee93adf794c91222ed7559f174f3cc74c5c" } } ], "extra": [ 1, 230, 227, 123, 29, 69, 182, 17, 224, 248, 28, 15, 168, 110, 164, 149, 64, 202, 4, 163, 180, 91, 17, 168, 74, 243, 244, 175, 132, 24, 209, 173, 110, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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