Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 263d92e2600cbdc770f8a495b954c4ea7cb531bb62e51924ab10abd75a64924b

Tx prefix hash: 67602c5ac5878d92cd7566aa427f9c90a95f7d7e28edc31d32adf434c5e2282e
Tx public key: 21a6e29ec536e6bba1a2aed03c7cd107b317013fcb1e2cf51fca899d8e859f8f
Timestamp: 1765653420 Timestamp [UCT]: 2025-12-13 19:17:00 Age [y:d:h:m:s]: 00:045:04:53:21
Block: 1432908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32185 RingCT/type: yes/0
Extra: 0121a6e29ec536e6bba1a2aed03c7cd107b317013fcb1e2cf51fca899d8e859f8f02110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2c3ed8324dbe2037363b5d58bb39b40d5d31a2faaaec3e8afbff4ddd6e7992 0.600000000000 1921687 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": 1432918, "vin": [ { "gen": { "height": 1432908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2c3ed8324dbe2037363b5d58bb39b40d5d31a2faaaec3e8afbff4ddd6e7992" } } ], "extra": [ 1, 33, 166, 226, 158, 197, 54, 230, 187, 161, 162, 174, 208, 60, 124, 209, 7, 179, 23, 1, 63, 203, 30, 44, 245, 31, 202, 137, 157, 142, 133, 159, 143, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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