Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bcff32c29713da611678931206b97bcc9dfccabfc80ea395ac44767c603f0c5

Tx prefix hash: c8c88a7d3c66cd2024edebcbabc081df2d780bf2f4ee3c7d3f330a12b1290db3
Tx public key: 4644718d4edcd08f8955490cd913047b84abaa1f02e192c86e586b4a6a2fd71a
Timestamp: 1653303297 Timestamp [UCT]: 2022-05-23 10:54:57 Age [y:d:h:m:s]: 02:181:11:31:42
Block: 507122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 650291 RingCT/type: yes/0
Extra: 014644718d4edcd08f8955490cd913047b84abaa1f02e192c86e586b4a6a2fd71a02110000000da8c141c5000000000000000000

1 output(s) for total of 12.816128361000 dcy

stealth address amount amount idx
00: 761943da47ab7a790736c7efacb0eb80bc5d610fc14e682cacbe531ca217e9c8 12.816128361000 932813 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": 507132, "vin": [ { "gen": { "height": 507122 } } ], "vout": [ { "amount": 12816128361, "target": { "key": "761943da47ab7a790736c7efacb0eb80bc5d610fc14e682cacbe531ca217e9c8" } } ], "extra": [ 1, 70, 68, 113, 141, 78, 220, 208, 143, 137, 85, 73, 12, 217, 19, 4, 123, 132, 171, 170, 31, 2, 225, 146, 200, 110, 88, 107, 74, 106, 47, 215, 26, 2, 17, 0, 0, 0, 13, 168, 193, 65, 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