Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28b11d147cd377e99d1e50edd2da88047a06845d726c0608a5074fc490f1414f

Tx prefix hash: af0e4ef25ff58738c84278e51a6d0cb7613b230aadb63bec1b593d5dc5f626e1
Tx public key: 69c6c03696b1eacc3db47ebed5e30aca3bdca92b4b8344f1ad6fb5723a1d9b25
Timestamp: 1765907707 Timestamp [UCT]: 2025-12-16 17:55:07 Age [y:d:h:m:s]: 00:023:01:47:59
Block: 1435007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16544 RingCT/type: yes/0
Extra: 0169c6c03696b1eacc3db47ebed5e30aca3bdca92b4b8344f1ad6fb5723a1d9b25021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 426b819d2a6bafc91474339d2ab16838259f102d1774cfd14c232b83e6520f5c 0.600000000000 1923804 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": 1435017, "vin": [ { "gen": { "height": 1435007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "426b819d2a6bafc91474339d2ab16838259f102d1774cfd14c232b83e6520f5c" } } ], "extra": [ 1, 105, 198, 192, 54, 150, 177, 234, 204, 61, 180, 126, 190, 213, 227, 10, 202, 59, 220, 169, 43, 75, 131, 68, 241, 173, 111, 181, 114, 58, 29, 155, 37, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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