Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9589e9e6290ddafe49731f9cc206d4508cac82f07a9c5ec5f0dc4739fd569279

Tx prefix hash: 7f748d82fb1f35d44bec1908761267500fa7a994c437e1c836a00492140d5d2c
Tx public key: 406d91870b7c57b938a7d07f4375acde3acf3b104d061ac559c558d071b51bf6
Timestamp: 1720520644 Timestamp [UCT]: 2024-07-09 10:24:04 Age [y:d:h:m:s]: 01:124:04:20:26
Block: 1061878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347275 RingCT/type: yes/0
Extra: 01406d91870b7c57b938a7d07f4375acde3acf3b104d061ac559c558d071b51bf602110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb31b9028e941675cbe509f579f5f1c6d35f4a949b1bae123c2a1ab9c2b21fc0 0.600000000000 1532377 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": 1061888, "vin": [ { "gen": { "height": 1061878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb31b9028e941675cbe509f579f5f1c6d35f4a949b1bae123c2a1ab9c2b21fc0" } } ], "extra": [ 1, 64, 109, 145, 135, 11, 124, 87, 185, 56, 167, 208, 127, 67, 117, 172, 222, 58, 207, 59, 16, 77, 6, 26, 197, 89, 197, 88, 208, 113, 181, 27, 246, 2, 17, 0, 0, 0, 11, 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