Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 336ee2cf8d8dc50f1ba88db859e5ece776a9b80bdd3479295f269e7d745f92e6

Tx prefix hash: e56a8043f1d635f95ef6ed8f84944940691129f38d990206c377b57f804bd0e5
Tx public key: 7bc9747c35ad019d9d1e4a80257804a1f87bc0837d29ac016f50b8714ad9567f
Timestamp: 1725924432 Timestamp [UCT]: 2024-09-09 23:27:12 Age [y:d:h:m:s]: 00:188:06:36:52
Block: 1106673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134403 RingCT/type: yes/0
Extra: 017bc9747c35ad019d9d1e4a80257804a1f87bc0837d29ac016f50b8714ad9567f021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9a9083b26e2a66c0e53b0a4a9eed8ee330cf69a50429587c976c9c599745b3d 0.600000000000 1584274 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": 1106683, "vin": [ { "gen": { "height": 1106673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9a9083b26e2a66c0e53b0a4a9eed8ee330cf69a50429587c976c9c599745b3d" } } ], "extra": [ 1, 123, 201, 116, 124, 53, 173, 1, 157, 157, 30, 74, 128, 37, 120, 4, 161, 248, 123, 192, 131, 125, 41, 172, 1, 111, 80, 184, 113, 74, 217, 86, 127, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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