Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395a9433cac1f012b4cdb55d42ac047c96c514ff1fe708336509c086f1dcd54d

Tx prefix hash: c2b6f903faad677e54c79f49bb15c103bd22a0fe9b5d8d34f47f2197840975cb
Tx public key: 7b5f6adbc56ad60262e282113d1ddd9cb0fdfea410784a93699389482102be84
Timestamp: 1723682631 Timestamp [UCT]: 2024-08-15 00:43:51 Age [y:d:h:m:s]: 00:235:14:31:49
Block: 1088085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168265 RingCT/type: yes/0
Extra: 017b5f6adbc56ad60262e282113d1ddd9cb0fdfea410784a93699389482102be8402110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e37a3db3290319eb2660476237e0e3c901bb6cbc29821e8e7796e8cadd3ed72e 0.600000000000 1562698 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": 1088095, "vin": [ { "gen": { "height": 1088085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e37a3db3290319eb2660476237e0e3c901bb6cbc29821e8e7796e8cadd3ed72e" } } ], "extra": [ 1, 123, 95, 106, 219, 197, 106, 214, 2, 98, 226, 130, 17, 61, 29, 221, 156, 176, 253, 254, 164, 16, 120, 74, 147, 105, 147, 137, 72, 33, 2, 190, 132, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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