Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ee9f91d0dc8fe03043d1851cc3dadc74e3577a6b1c3c54d12fdabb16ffec762

Tx prefix hash: 974e34ba9905666dbba7023f80dc700168a0aa4a95c89144b15808590c069846
Tx public key: cc17f2b11a72d87883f621e1faa77690822eaed12079884537e509e7c13123f4
Timestamp: 1581946226 Timestamp [UCT]: 2020-02-17 13:30:26 Age [y:d:h:m:s]: 04:316:00:30:45
Block: 66648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118398 RingCT/type: yes/0
Extra: 01cc17f2b11a72d87883f621e1faa77690822eaed12079884537e509e7c13123f402110000000112c4732d000000000000000000

1 output(s) for total of 369.120629385000 dcy

stealth address amount amount idx
00: 6f4975407c31193609a6c071f531dbbe0f6a76ee1cdb7275e1c797dc1d8a9b9f 369.120629385000 122795 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": 66658, "vin": [ { "gen": { "height": 66648 } } ], "vout": [ { "amount": 369120629385, "target": { "key": "6f4975407c31193609a6c071f531dbbe0f6a76ee1cdb7275e1c797dc1d8a9b9f" } } ], "extra": [ 1, 204, 23, 242, 177, 26, 114, 216, 120, 131, 246, 33, 225, 250, 167, 118, 144, 130, 46, 174, 209, 32, 121, 136, 69, 55, 229, 9, 231, 193, 49, 35, 244, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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