Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705b6cdeffeca11fe2b8ac1ed55b4113180655562002b26fb2ce19a2d8035b7f

Tx prefix hash: 495ad1548a3d4dd9a904829a2a45533e9dc6ae497bffa863bf90a4d09c12708e
Tx public key: 937c959b497b82142fdaa95118a6cd76f8aed2e73320a3de2e6c5c7fe513ff5a
Timestamp: 1574095457 Timestamp [UCT]: 2019-11-18 16:44:17 Age [y:d:h:m:s]: 05:008:19:36:27
Block: 11816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1149581 RingCT/type: yes/0
Extra: 01937c959b497b82142fdaa95118a6cd76f8aed2e73320a3de2e6c5c7fe513ff5a021100000002ccefb800000000000000000000

1 output(s) for total of 560.853682525000 dcy

stealth address amount amount idx
00: 80b49c4b884a9b0e6f871b968a84c9e4bc0f7d7a5c90e33966f8bae35fb9557f 560.853682525000 12899 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": 11826, "vin": [ { "gen": { "height": 11816 } } ], "vout": [ { "amount": 560853682525, "target": { "key": "80b49c4b884a9b0e6f871b968a84c9e4bc0f7d7a5c90e33966f8bae35fb9557f" } } ], "extra": [ 1, 147, 124, 149, 155, 73, 123, 130, 20, 47, 218, 169, 81, 24, 166, 205, 118, 248, 174, 210, 231, 51, 32, 163, 222, 46, 108, 92, 127, 229, 19, 255, 90, 2, 17, 0, 0, 0, 2, 204, 239, 184, 0, 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