Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc34f8a1a59b8460f4ab5019fe66b06976241c568059786a13c370332db28d7e

Tx prefix hash: a833ea7fbf1bbaf7e3e99b5fb9eccd191906fabe0815d971ec361d8e0bb9a4c2
Tx public key: a6dc20e9dd90514b1e6f9ef75181f38a8f9f6e28b4b0f4848a051ff89befd5c3
Timestamp: 1707381974 Timestamp [UCT]: 2024-02-08 08:46:14 Age [y:d:h:m:s]: 00:259:15:36:21
Block: 952931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185965 RingCT/type: yes/0
Extra: 01a6dc20e9dd90514b1e6f9ef75181f38a8f9f6e28b4b0f4848a051ff89befd5c30211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c67734a316a1caaa61267cb4e9aca62c1e8fe3353e225dc740a88a19089e965 0.600000000000 1412077 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": 952941, "vin": [ { "gen": { "height": 952931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c67734a316a1caaa61267cb4e9aca62c1e8fe3353e225dc740a88a19089e965" } } ], "extra": [ 1, 166, 220, 32, 233, 221, 144, 81, 75, 30, 111, 158, 247, 81, 129, 243, 138, 143, 159, 110, 40, 180, 176, 244, 132, 138, 5, 31, 248, 155, 239, 213, 195, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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