Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fa0c22a9fa43f519ff018286aaf20bfb3920da1ef96debfcdbf7d505c8dab9e

Tx prefix hash: ede5b4e8e37a564f56886504d3d17393be1832c5dbe20c208261c396ecf50479
Tx public key: 106627663513f1f616d044a1b3aeffe29ac584badb26c972a461451848a447a8
Timestamp: 1685403284 Timestamp [UCT]: 2023-05-29 23:34:44 Age [y:d:h:m:s]: 02:020:18:55:44
Block: 770985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536841 RingCT/type: yes/0
Extra: 01106627663513f1f616d044a1b3aeffe29ac584badb26c972a461451848a447a802110000000775e3f0e9000000000000000000

1 output(s) for total of 1.711617887000 dcy

stealth address amount amount idx
00: 69916da5c2f1c3b68cc502714fac48ff6c5228dc9bf7154a98ab39a7df49e4e0 1.711617887000 1220324 of 0

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": 770995, "vin": [ { "gen": { "height": 770985 } } ], "vout": [ { "amount": 1711617887, "target": { "key": "69916da5c2f1c3b68cc502714fac48ff6c5228dc9bf7154a98ab39a7df49e4e0" } } ], "extra": [ 1, 16, 102, 39, 102, 53, 19, 241, 246, 22, 208, 68, 161, 179, 174, 255, 226, 154, 197, 132, 186, 219, 38, 201, 114, 164, 97, 69, 24, 72, 164, 71, 168, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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