Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63314dbb66610db593d346c913144da299d5b24a0928a9722b67b4182c500ef7

Tx prefix hash: f90a40f764932d752f28ac9fd4b27138653a938a9a1e6a95d1b7b8239eb2c628
Tx public key: e92598937df7ad4353cc640d4a2d74b288875a71f4807cfc9aaa5ac6ce533707
Timestamp: 1707966473 Timestamp [UCT]: 2024-02-15 03:07:53 Age [y:d:h:m:s]: 01:086:14:17:24
Block: 957780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322957 RingCT/type: yes/0
Extra: 01e92598937df7ad4353cc640d4a2d74b288875a71f4807cfc9aaa5ac6ce53370702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0e9f7755a8216388ae487fe10ff5a7fd28a1c08d9f4ca70d7157b74d911ed52 0.600000000000 1417129 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": 957790, "vin": [ { "gen": { "height": 957780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0e9f7755a8216388ae487fe10ff5a7fd28a1c08d9f4ca70d7157b74d911ed52" } } ], "extra": [ 1, 233, 37, 152, 147, 125, 247, 173, 67, 83, 204, 100, 13, 74, 45, 116, 178, 136, 135, 90, 113, 244, 128, 124, 252, 154, 170, 90, 198, 206, 83, 55, 7, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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