← previous blocknext block →recent activity
Analyzing
Block #88,192,832
13 transactions · 11 stateful · 2026-07-16 19:26:37 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,192,832 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eef368f…aa21
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xebbcae2a…16f8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5b0b6826…ef3c
0x34b655…2a6f
4 touches
1 conflict
0x3e086259…8d37
0x34b655…2a6f
2 touches
0 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x8eef368f1b…01aa21
Audit this contract →
← previous block·next block →recent activity