Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c0cec49e62f326d3224f991060148b677f421f42e0d2d97d38fcdc6e13fb4a

Tx prefix hash: e9c4624a9e870c7dc313e8a5178395d70ec1a425c831d4391853bd141682999a
Tx public key: c04796117b70b5f86742b56ad05b9c60550133ff523ca5ea308f85552f6d146e
Timestamp: 1660492503 Timestamp [UCT]: 2022-08-14 15:55:03 Age [y:d:h:m:s]: 02:217:18:55:47
Block: 565768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 676887 RingCT/type: yes/0
Extra: 01c04796117b70b5f86742b56ad05b9c60550133ff523ca5ea308f85552f6d146e021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.191734418000 dcy

stealth address amount amount idx
00: af61130af91be56c6356984300ae1903ecdd587f8c9e6833a7293a6c47616ccd 8.191734418000 998688 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": 565778, "vin": [ { "gen": { "height": 565768 } } ], "vout": [ { "amount": 8191734418, "target": { "key": "af61130af91be56c6356984300ae1903ecdd587f8c9e6833a7293a6c47616ccd" } } ], "extra": [ 1, 192, 71, 150, 17, 123, 112, 181, 248, 103, 66, 181, 106, 208, 91, 156, 96, 85, 1, 51, 255, 82, 60, 165, 234, 48, 143, 133, 85, 47, 109, 20, 110, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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