Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ff87fbf4c292ac1e2777895f638090761a7a7ed60e1845aa3ceca238276b443

Tx prefix hash: fe2f889803e4191d4fb53012bde6fe63e55f85c3527e4e660dda5f9510dfbb8d
Tx public key: 70a7fb77aecc742590838a1fcc57cdb9a48ae4c9244230929fff95d19cfde39f
Timestamp: 1755962113 Timestamp [UCT]: 2025-08-23 15:15:13 Age [y:d:h:m:s]: 00:085:02:17:50
Block: 1352776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60749 RingCT/type: yes/0
Extra: 0170a7fb77aecc742590838a1fcc57cdb9a48ae4c9244230929fff95d19cfde39f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a9db1e905b946c566e9c5f61fd165abc0d125ce8401f626e1abf8fe74c232e 0.600000000000 1840743 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": 1352786, "vin": [ { "gen": { "height": 1352776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a9db1e905b946c566e9c5f61fd165abc0d125ce8401f626e1abf8fe74c232e" } } ], "extra": [ 1, 112, 167, 251, 119, 174, 204, 116, 37, 144, 131, 138, 31, 204, 87, 205, 185, 164, 138, 228, 201, 36, 66, 48, 146, 159, 255, 149, 209, 156, 253, 227, 159, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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