Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af52b20d0d45a59b4d92b4b0cb23514c1989446ab8a26e95e8b1522908f3ec53

Tx prefix hash: 87bab15d42c3c608d2bb533595c676b3593acca8e79680216ef2b69320144f58
Tx public key: 102812d49ff4a7c41cff6eddd387413b19f0eea6e5a7c642ead4bc0f82d19403
Timestamp: 1708573157 Timestamp [UCT]: 2024-02-22 03:39:17 Age [y:d:h:m:s]: 01:048:04:29:39
Block: 962819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295466 RingCT/type: yes/0
Extra: 01102812d49ff4a7c41cff6eddd387413b19f0eea6e5a7c642ead4bc0f82d1940302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 419e4821f780eb4d4854cfeb3f877619f7fd4ee9f6b346161800e155e053e7a7 0.600000000000 1422504 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": 962829, "vin": [ { "gen": { "height": 962819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "419e4821f780eb4d4854cfeb3f877619f7fd4ee9f6b346161800e155e053e7a7" } } ], "extra": [ 1, 16, 40, 18, 212, 159, 244, 167, 196, 28, 255, 110, 221, 211, 135, 65, 59, 25, 240, 238, 166, 229, 167, 198, 66, 234, 212, 188, 15, 130, 209, 148, 3, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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