Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05feaf9933273279bcb15127ffccc865b42aa3891edd4b51ae60b0fa7f3f0422

Tx prefix hash: edf77ba39bbb788b47ddd417777c7d6c3e8e6b30def97cec365603d4b30e9302
Tx public key: 9f7e6a5e3da4ca77b92a69f81ed7bc89d1d78be163d25eb4cbd9e310297f6d5a
Timestamp: 1716213608 Timestamp [UCT]: 2024-05-20 14:00:08 Age [y:d:h:m:s]: 00:282:00:12:40
Block: 1026166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201538 RingCT/type: yes/0
Extra: 019f7e6a5e3da4ca77b92a69f81ed7bc89d1d78be163d25eb4cbd9e310297f6d5a02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb0daf396258b20cc641b1f0d45a90f37522280f21f070d97f9b412cd28298f8 0.600000000000 1493103 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": 1026176, "vin": [ { "gen": { "height": 1026166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb0daf396258b20cc641b1f0d45a90f37522280f21f070d97f9b412cd28298f8" } } ], "extra": [ 1, 159, 126, 106, 94, 61, 164, 202, 119, 185, 42, 105, 248, 30, 215, 188, 137, 209, 215, 139, 225, 99, 210, 94, 180, 203, 217, 227, 16, 41, 127, 109, 90, 2, 17, 0, 0, 0, 6, 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