Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fb9138e929fc28796ac61a9680f591da8ebfa321c31ce05a59cbef2e93d99f8

Tx prefix hash: 3e8dd033617574dd205e7cda50fd1f8183ec17d05e9aa6c23eb96ed6ece70c75
Tx public key: 75e703e867cc91fd97d58257cfc72aabfa496b548954ada5cac3a82237751dc9
Timestamp: 1687034218 Timestamp [UCT]: 2023-06-17 20:36:58 Age [y:d:h:m:s]: 01:331:06:04:17
Block: 784507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497936 RingCT/type: yes/0
Extra: 0175e703e867cc91fd97d58257cfc72aabfa496b548954ada5cac3a82237751dc9021100000002272bcc39000000000000000000

1 output(s) for total of 1.543841806000 dcy

stealth address amount amount idx
00: 466ede0e9be7c08e0f042cdc2e4c7c03348d81ad58cbc96bcc43af9d3e10c9d8 1.543841806000 1234396 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": 784517, "vin": [ { "gen": { "height": 784507 } } ], "vout": [ { "amount": 1543841806, "target": { "key": "466ede0e9be7c08e0f042cdc2e4c7c03348d81ad58cbc96bcc43af9d3e10c9d8" } } ], "extra": [ 1, 117, 231, 3, 232, 103, 204, 145, 253, 151, 213, 130, 87, 207, 199, 42, 171, 250, 73, 107, 84, 137, 84, 173, 165, 202, 195, 168, 34, 55, 117, 29, 201, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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