Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33f0e16269b5f046cbc77c15895a2b4edb23e30ffeb5d19f44397fb6108cc56d

Tx prefix hash: 3f5bf2c180daf21c7feebfde7c9a11508dee4c95fb94fac61accec9e13a3c3e7
Tx public key: 8fc9d300f101df7ab3ebce7ec3e81a1633337afa31e61e85c2cccabf1e52ca32
Timestamp: 1691093279 Timestamp [UCT]: 2023-08-03 20:07:59 Age [y:d:h:m:s]: 01:249:20:37:23
Block: 818170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439655 RingCT/type: yes/0
Extra: 018fc9d300f101df7ab3ebce7ec3e81a1633337afa31e61e85c2cccabf1e52ca3202110000000675e3f0e9000000000000000000

1 output(s) for total of 1.194162021000 dcy

stealth address amount amount idx
00: b9ea48518138d29d5921501ffadd4cbb234ffa6f2da50cb8ecc61e5976912d78 1.194162021000 1270112 of 0

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": 818180, "vin": [ { "gen": { "height": 818170 } } ], "vout": [ { "amount": 1194162021, "target": { "key": "b9ea48518138d29d5921501ffadd4cbb234ffa6f2da50cb8ecc61e5976912d78" } } ], "extra": [ 1, 143, 201, 211, 0, 241, 1, 223, 122, 179, 235, 206, 126, 195, 232, 26, 22, 51, 51, 122, 250, 49, 230, 30, 133, 194, 204, 202, 191, 30, 82, 202, 50, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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