Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705ee07157075c1a1b80de28a7ec5d540be15c8579f52c2b614e7b1376e99336

Tx prefix hash: fd3b300c1e284304729abfd9afe563359cc322f1210a88377550d4953b3c48aa
Tx public key: 96609ce1c3f2ed6d1835b1e7888d49a6ecd777b92d6c601c29075088e0c92b61
Timestamp: 1759996373 Timestamp [UCT]: 2025-10-09 07:52:53 Age [y:d:h:m:s]: 00:075:16:24:28
Block: 1386021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54186 RingCT/type: yes/0
Extra: 0196609ce1c3f2ed6d1835b1e7888d49a6ecd777b92d6c601c29075088e0c92b6102110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16fc241bb68a3df14b1afdb70066f7769c0425c0fc9f857aaede74c169143e1c 0.600000000000 1874184 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": 1386031, "vin": [ { "gen": { "height": 1386021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16fc241bb68a3df14b1afdb70066f7769c0425c0fc9f857aaede74c169143e1c" } } ], "extra": [ 1, 150, 96, 156, 225, 195, 242, 237, 109, 24, 53, 177, 231, 136, 141, 73, 166, 236, 215, 119, 185, 45, 108, 96, 28, 41, 7, 80, 136, 224, 201, 43, 97, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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