Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5616c9cfd5150e331b2a4b40bb9a5933c036ca6a8ba172ce11c7db3339beece1

Tx prefix hash: 2a831ed762ef4da0d2e05374f08daf0d705da987245a3687bc107ec81e4f790e
Tx public key: a6b9a3b5466b22ec992369d4ebd9d836bba75e04e9fa45cced106e4a52475e84
Timestamp: 1746161691 Timestamp [UCT]: 2025-05-02 04:54:51 Age [y:d:h:m:s]: 00:203:09:47:28
Block: 1273928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143085 RingCT/type: yes/0
Extra: 01a6b9a3b5466b22ec992369d4ebd9d836bba75e04e9fa45cced106e4a52475e84021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9beb877c8bb044ff236e53c3fb6ea707d06a4fc0c2b8f1cb175de12915a376b3 0.600000000000 1761215 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": 1273938, "vin": [ { "gen": { "height": 1273928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9beb877c8bb044ff236e53c3fb6ea707d06a4fc0c2b8f1cb175de12915a376b3" } } ], "extra": [ 1, 166, 185, 163, 181, 70, 107, 34, 236, 153, 35, 105, 212, 235, 217, 216, 54, 187, 167, 94, 4, 233, 250, 69, 204, 237, 16, 110, 74, 82, 71, 94, 132, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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