Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070e3da9a50e7ac7504848a411f08467af14289aa0efabdb2bd25eb32676c2b7

Tx prefix hash: 3ab308926deef43eda377577b8d91f7c50544ced8c67a8a9b06984179281d563
Tx public key: e86d5b75786e5f37a3c9f044f1dd937068d73041c8fa8114ca77e1b0054d8a9a
Timestamp: 1719905418 Timestamp [UCT]: 2024-07-02 07:30:18 Age [y:d:h:m:s]: 00:275:18:19:14
Block: 1056773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197022 RingCT/type: yes/0
Extra: 01e86d5b75786e5f37a3c9f044f1dd937068d73041c8fa8114ca77e1b0054d8a9a021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cb183e7567d0ba9a78fc9dbe24396f57fe56c5e6bb609bad35b09a1dd634f5c 0.600000000000 1527198 of 15

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": 1056783, "vin": [ { "gen": { "height": 1056773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cb183e7567d0ba9a78fc9dbe24396f57fe56c5e6bb609bad35b09a1dd634f5c" } } ], "extra": [ 1, 232, 109, 91, 117, 120, 110, 95, 55, 163, 201, 240, 68, 241, 221, 147, 112, 104, 215, 48, 65, 200, 250, 129, 20, 202, 119, 225, 176, 5, 77, 138, 154, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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