Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd741d0e68b211084731bfafd373ebcde51b98d76c0047b7d55f04dc4939d4b5

Tx prefix hash: 266396aaeda481d5c03c764e06d0820d05a79d354b1761ce4ea6ac3a599979cb
Tx public key: 884c3c181afe9cf3892604b05365e7a9b70a2bc4807866b91d55eb4ec81acc7a
Timestamp: 1580621549 Timestamp [UCT]: 2020-02-02 05:32:29 Age [y:d:h:m:s]: 04:278:08:06:13
Block: 56911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090205 RingCT/type: yes/0
Extra: 01884c3c181afe9cf3892604b05365e7a9b70a2bc4807866b91d55eb4ec81acc7a021100000002b221b3d1000000000000000000

1 output(s) for total of 397.585973982000 dcy

stealth address amount amount idx
00: 9f82b871f9deb085ea1e7953cabd76f269f57e29bb0c18d3d62bc0f61b89e61c 397.585973982000 104940 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": 56921, "vin": [ { "gen": { "height": 56911 } } ], "vout": [ { "amount": 397585973982, "target": { "key": "9f82b871f9deb085ea1e7953cabd76f269f57e29bb0c18d3d62bc0f61b89e61c" } } ], "extra": [ 1, 136, 76, 60, 24, 26, 254, 156, 243, 137, 38, 4, 176, 83, 101, 231, 169, 183, 10, 43, 196, 128, 120, 102, 185, 29, 85, 235, 78, 200, 26, 204, 122, 2, 17, 0, 0, 0, 2, 178, 33, 179, 209, 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