Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a7dca3f99f6a8c9ecaa5a1587e5f08a260ae97d927bbbf7a55f86352829e53

Tx prefix hash: 4c2dd4b9359b8f7bff2cecdc62930ae0eae1a237d5e6aeb6ff987d457c46f12b
Tx public key: f5306631f241a4a7a77ae8c05207cce21674e821ee9f4aebb2a770a72a77a31f
Timestamp: 1733575339 Timestamp [UCT]: 2024-12-07 12:42:19 Age [y:d:h:m:s]: 00:118:20:49:19
Block: 1169996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84755 RingCT/type: yes/0
Extra: 01f5306631f241a4a7a77ae8c05207cce21674e821ee9f4aebb2a770a72a77a31f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5c1190152763633adb71329888fa453c84f37bbfeffcd263288513cadc29e32 0.600000000000 1655723 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": 1170006, "vin": [ { "gen": { "height": 1169996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5c1190152763633adb71329888fa453c84f37bbfeffcd263288513cadc29e32" } } ], "extra": [ 1, 245, 48, 102, 49, 242, 65, 164, 167, 167, 122, 232, 192, 82, 7, 204, 226, 22, 116, 232, 33, 238, 159, 74, 235, 178, 167, 112, 167, 42, 119, 163, 31, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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