← previous blocknext block →recent activity
Analyzing
Block #91,432,417
21 transactions · 18 stateful · 2026-07-29 19:55:37 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,432,417 · 21 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
4w05w06w010w111w213w014w115w317w318w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x60e67008…f6aa
0x34b655…2a6f
6 touches
3 conflicts
0x5d494c83…a65e
0x34b655…2a6f
4 touches
1 conflict
0x6e6b8ec7…2197
0x34b655…2a6f
4 touches
1 conflict
0x6f232437…749d
0x34b655…2a6f
4 touches
1 conflict
0x73f113ea…7cab
0x34b655…2a6f
4 touches
1 conflict
0x7d0c7575…db47
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity