Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864fb7e6a40e486c6e5f085642d29365f41e10b0c7662ae6df5fe52197827edb

Tx prefix hash: a99fc5e767c48b2014cf6c941d9cd537309d0234073c9b53d257d9f73c5d5f66
Tx public key: 4c0f83df5806eb54d0e7bb3f1b17b25f52e461de4f652456fdcc41dea88e0df6
Timestamp: 1729664370 Timestamp [UCT]: 2024-10-23 06:19:30 Age [y:d:h:m:s]: 00:032:01:18:04
Block: 1137643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22901 RingCT/type: yes/0
Extra: 014c0f83df5806eb54d0e7bb3f1b17b25f52e461de4f652456fdcc41dea88e0df6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a67081802c62db42f27df8449b24fd9e3b9482e0c10cf4066f96226ea0098ec 0.600000000000 1621172 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": 1137653, "vin": [ { "gen": { "height": 1137643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a67081802c62db42f27df8449b24fd9e3b9482e0c10cf4066f96226ea0098ec" } } ], "extra": [ 1, 76, 15, 131, 223, 88, 6, 235, 84, 208, 231, 187, 63, 27, 23, 178, 95, 82, 228, 97, 222, 79, 101, 36, 86, 253, 204, 65, 222, 168, 142, 13, 246, 2, 17, 0, 0, 0, 2, 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