Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e294c27507b6d4a7001ce7f1f894d2043f7f9b20175db3285a325284511c72

Tx prefix hash: 17f230f8f8b814189cc610af90d0210ef7583e3eb1aa71aade5f2e6707f73c0e
Tx public key: ee0fc1df53aa0e20125a0ae19694d00752addd21d7dd2708eda1b3187a2b7f06
Timestamp: 1760923722 Timestamp [UCT]: 2025-10-20 01:28:42 Age [y:d:h:m:s]: 00:020:18:10:38
Block: 1393733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14850 RingCT/type: yes/0
Extra: 01ee0fc1df53aa0e20125a0ae19694d00752addd21d7dd2708eda1b3187a2b7f06021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2759e295cb849a87c0105fddc6172df29f5981dfb7485869cb61ba371c519da9 0.600000000000 1881998 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": 1393743, "vin": [ { "gen": { "height": 1393733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2759e295cb849a87c0105fddc6172df29f5981dfb7485869cb61ba371c519da9" } } ], "extra": [ 1, 238, 15, 193, 223, 83, 170, 14, 32, 18, 90, 10, 225, 150, 148, 208, 7, 82, 173, 221, 33, 215, 221, 39, 8, 237, 161, 179, 24, 122, 43, 127, 6, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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