Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d75cd74898a6c23f615f6d48769acb1c5ecce526df857ec31aa9a17328dbb386

Tx prefix hash: 7b9d0d5445ae12beaa59862a5c3f5739bb962712611a7edff1dcbd1d726cceba
Tx public key: a9f49ec1ec28057c494fe9fd3f158bdf131a6c5bc0c9f1324027b986c5835f21
Timestamp: 1708418005 Timestamp [UCT]: 2024-02-20 08:33:25 Age [y:d:h:m:s]: 01:119:00:47:31
Block: 961538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346025 RingCT/type: yes/0
Extra: 01a9f49ec1ec28057c494fe9fd3f158bdf131a6c5bc0c9f1324027b986c5835f21021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7d74a90ddeb2f9b179e3b4c27946ddf2786f9bae873b3c12be465bc6aa37c6 0.600000000000 1421149 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": 961548, "vin": [ { "gen": { "height": 961538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7d74a90ddeb2f9b179e3b4c27946ddf2786f9bae873b3c12be465bc6aa37c6" } } ], "extra": [ 1, 169, 244, 158, 193, 236, 40, 5, 124, 73, 79, 233, 253, 63, 21, 139, 223, 19, 26, 108, 91, 192, 201, 241, 50, 64, 39, 185, 134, 197, 131, 95, 33, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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