Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6ee3a2e5d027252ef138da3894b918d13a92e645957d901b9dd555cdab1e798

Tx prefix hash: 806d53f96f6867ca9bf32de8bbdeac03015dd1e048bb66b6d1d3f45ecba64c3d
Tx public key: 658f93ec5c434aee92022e29c7c8155f5f6d85c58705b4536447f0c7874998d8
Timestamp: 1661325634 Timestamp [UCT]: 2022-08-24 07:20:34 Age [y:d:h:m:s]: 02:173:05:29:01
Block: 572636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645031 RingCT/type: yes/0
Extra: 01658f93ec5c434aee92022e29c7c8155f5f6d85c58705b4536447f0c7874998d802110000000133af99f4000000000000000000

1 output(s) for total of 7.773548609000 dcy

stealth address amount amount idx
00: a0c093f912e655343e28a592a0f1bc0c8bddb577c27aa6cacbea4bc85390bb19 7.773548609000 1005894 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": 572646, "vin": [ { "gen": { "height": 572636 } } ], "vout": [ { "amount": 7773548609, "target": { "key": "a0c093f912e655343e28a592a0f1bc0c8bddb577c27aa6cacbea4bc85390bb19" } } ], "extra": [ 1, 101, 143, 147, 236, 92, 67, 74, 238, 146, 2, 46, 41, 199, 200, 21, 95, 95, 109, 133, 197, 135, 5, 180, 83, 100, 71, 240, 199, 135, 73, 152, 216, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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