Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96340041cdb8efd48273a5ba870ba10425cd7ae4958c6fbfdca452a5381733a3

Tx prefix hash: d322ca92b074052ffd21a1dbde398e3aeb67683fdb14fd39e24f46109c2552de
Tx public key: b8b516f7ea1355d827938277acf25ccafc7c5b5a2d69772002a720129b8fb056
Timestamp: 1704381519 Timestamp [UCT]: 2024-01-04 15:18:39 Age [y:d:h:m:s]: 01:163:16:33:49
Block: 928075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378028 RingCT/type: yes/0
Extra: 01b8b516f7ea1355d827938277acf25ccafc7c5b5a2d69772002a720129b8fb05602110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36663ffc9a79a7c7fcbad355bc5151133c8b65c4b1eba19b20c7fb4341a16d99 0.600000000000 1385931 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": 928085, "vin": [ { "gen": { "height": 928075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36663ffc9a79a7c7fcbad355bc5151133c8b65c4b1eba19b20c7fb4341a16d99" } } ], "extra": [ 1, 184, 181, 22, 247, 234, 19, 85, 216, 39, 147, 130, 119, 172, 242, 92, 202, 252, 124, 91, 90, 45, 105, 119, 32, 2, 167, 32, 18, 155, 143, 176, 86, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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