← previous blocknext block →recent activity
Analyzing
Block #91,288,281
17 transactions · 16 stateful · 2026-07-29 07:49:03 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,288,281 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w28w310w411w313w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x808129fc…f97d
0x34b655…2a6f
8 touches
6 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xcd0fdbef…b0d0
0x34b655…2a6f
6 touches
3 conflicts
0x5388bf7d…df61
0x34b655…2a6f
4 touches
1 conflict
0x59c77e51…7fcc
0x34b655…2a6f
4 touches
1 conflict
0x684d54a5…7e1c
0x34b655…2a6f
4 touches
1 conflict
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 0x808129fc27…daf97d
Audit this contract →
← previous block·next block →recent activity