Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f2de946aec2fad19b014a2ccc34ff9b56869a220b4d89d8ec8901fdaa6906f

Tx prefix hash: b0f2719ae2bcd07784990cafbfbce1cae3b0c62656b6d167fc6fec1734b93cc7
Tx public key: 4582a6bc00a5197f3f79d923d6b467706adec7aaf29798c58d80c9d6abae2026
Timestamp: 1709401841 Timestamp [UCT]: 2024-03-02 17:50:41 Age [y:d:h:m:s]: 01:220:05:10:57
Block: 969705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416051 RingCT/type: yes/0
Extra: 014582a6bc00a5197f3f79d923d6b467706adec7aaf29798c58d80c9d6abae202602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90a62f8ddee04c39e633e89f57e330ae4711d8746a620933e590fa4fbf4ed854 0.600000000000 1429542 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": 969715, "vin": [ { "gen": { "height": 969705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90a62f8ddee04c39e633e89f57e330ae4711d8746a620933e590fa4fbf4ed854" } } ], "extra": [ 1, 69, 130, 166, 188, 0, 165, 25, 127, 63, 121, 217, 35, 214, 180, 103, 112, 106, 222, 199, 170, 242, 151, 152, 197, 141, 128, 201, 214, 171, 174, 32, 38, 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