Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5859876ebf020e8059d9252f3d774fe60d0108d248afd0cd63aed6959e4ff35c

Tx prefix hash: fe3cf8570b8fb9749fbf308252e150a5cc937a503159e5fa82783b88daf98a6a
Tx public key: ad77c4b8bf67e1eba1b5052769b044af0d3b60413fc855268dd9297a284ee5bb
Timestamp: 1748888452 Timestamp [UCT]: 2025-06-02 18:20:52 Age [y:d:h:m:s]: 00:170:13:40:37
Block: 1296512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119593 RingCT/type: yes/0
Extra: 01ad77c4b8bf67e1eba1b5052769b044af0d3b60413fc855268dd9297a284ee5bb021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3b7dae3ecc6c7d286de4ded343c4a947ff90b0164883eca0ea0c27e3fcf255a 0.600000000000 1784023 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": 1296522, "vin": [ { "gen": { "height": 1296512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3b7dae3ecc6c7d286de4ded343c4a947ff90b0164883eca0ea0c27e3fcf255a" } } ], "extra": [ 1, 173, 119, 196, 184, 191, 103, 225, 235, 161, 181, 5, 39, 105, 176, 68, 175, 13, 59, 96, 65, 63, 200, 85, 38, 141, 217, 41, 122, 40, 78, 229, 187, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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