← previous blocknext block →recent activity
Analyzing
Block #96,132,029
28 transactions · 25 stateful · 2026-08-15 06:28:51 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.61
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,132,029 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w38w49w010w011w212w413w519w120w221w222w623w326w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x200ed648…912f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8a073405…7cc4
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 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
6 conflicts on slot 0x200ed6482b…21912f
Audit this contract →
← previous block·next block →recent activity