Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 922f297a8f61736afe1b910a0fed31dd0cdced371ea7740622812c96ba869d4e

Tx prefix hash: ec14c9f2d60ef379d133f94335aea041d41f1b7099a73527ae2c7d530de97601
Tx public key: 3b26505e322df848eb96eeb729135a7f9578aba8ccd0730692f6f4f877423312
Timestamp: 1657213870 Timestamp [UCT]: 2022-07-07 17:11:10 Age [y:d:h:m:s]: 02:256:06:16:00
Block: 538736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704301 RingCT/type: yes/0
Extra: 013b26505e322df848eb96eeb729135a7f9578aba8ccd0730692f6f4f8774233120211000000015eb576c5000000000000000000

1 output(s) for total of 10.068021651000 dcy

stealth address amount amount idx
00: 3c2a9e1b025018bdab0f638b920ec8c88146ff81afcfa236c1fbf4d0362d82fd 10.068021651000 968771 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": 538746, "vin": [ { "gen": { "height": 538736 } } ], "vout": [ { "amount": 10068021651, "target": { "key": "3c2a9e1b025018bdab0f638b920ec8c88146ff81afcfa236c1fbf4d0362d82fd" } } ], "extra": [ 1, 59, 38, 80, 94, 50, 45, 248, 72, 235, 150, 238, 183, 41, 19, 90, 127, 149, 120, 171, 168, 204, 208, 115, 6, 146, 246, 244, 248, 119, 66, 51, 18, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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