← previous blocknext block →recent activity
Analyzing
Block #83,036,091
56 transactions · 48 stateful · 2026-06-22 21:39:05 UTC
Parallelism
64/100
Blocked
77%
Avg conflicts / tx
3.54
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,036,091 · 56 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w08w110w211w313w414w515w617w718w819w937w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
28 touches
91 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xab83f300…f8c8
0x34b655…2a6f
10 touches
10 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
10 touches
10 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
10 touches
10 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
91 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity