Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c867ed22592cbf3df1ef90156a0533e71f26a6d211bde3a5cdef62cb1da1bcc

Tx prefix hash: 58ce370fa0cce5bd830d781671fb156b75f9d4d9cafadd45c3b78bf0ff5765a5
Tx public key: 333a3aa8b8250f7058003574d8304e7b24b63c32b4f0ae45502a724094ae022d
Timestamp: 1761438394 Timestamp [UCT]: 2025-10-26 00:26:34 Age [y:d:h:m:s]: 00:026:08:20:53
Block: 1397983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18845 RingCT/type: yes/0
Extra: 01333a3aa8b8250f7058003574d8304e7b24b63c32b4f0ae45502a724094ae022d021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45086f74d9a1246fc0dbf287d412308e8cb01de15e000995b7ecee4660583590 0.600000000000 1886276 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": 1397993, "vin": [ { "gen": { "height": 1397983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45086f74d9a1246fc0dbf287d412308e8cb01de15e000995b7ecee4660583590" } } ], "extra": [ 1, 51, 58, 58, 168, 184, 37, 15, 112, 88, 0, 53, 116, 216, 48, 78, 123, 36, 182, 60, 50, 180, 240, 174, 69, 80, 42, 114, 64, 148, 174, 2, 45, 2, 17, 0, 0, 0, 1, 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