Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6987f8bce7e895ff97e7cae4385b1c46b5884406aa3e70f4d29c38761542ed63

Tx prefix hash: 703bf27a9827850208c62aab0edc40c7d1507b84559524a7e380bfa99c0e4cb8
Tx public key: c30d8518c6c3ccc4bc84b5c8eda131c73c12b3273fa2107ced9334b82fa89687
Timestamp: 1719282541 Timestamp [UCT]: 2024-06-25 02:29:01 Age [y:d:h:m:s]: 00:324:01:05:00
Block: 1051599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231583 RingCT/type: yes/0
Extra: 01c30d8518c6c3ccc4bc84b5c8eda131c73c12b3273fa2107ced9334b82fa896870211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 739f3f2e3b9a5ea582532b5d1f1107e70eac467479473d6b136a1c4713f62f2f 0.600000000000 1521914 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": 1051609, "vin": [ { "gen": { "height": 1051599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "739f3f2e3b9a5ea582532b5d1f1107e70eac467479473d6b136a1c4713f62f2f" } } ], "extra": [ 1, 195, 13, 133, 24, 198, 195, 204, 196, 188, 132, 181, 200, 237, 161, 49, 199, 60, 18, 179, 39, 63, 162, 16, 124, 237, 147, 52, 184, 47, 168, 150, 135, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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