← previous blocknext block →recent activity
Analyzing
Block #91,126,808
17 transactions · 14 stateful · 2026-07-28 18:15:53 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,126,808 · 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
1w05w07w08w19w210w311w112w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb3f6210…2c83
0x34b655…2a6f
8 touches
6 conflicts
0xa779293b…5e59
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0xbd765aea…6fda
0x34b655…2a6f
6 touches
3 conflicts
0x4f412a3d…b1f7
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67b
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67c
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 0xdb3f621073…082c83
Audit this contract →
← previous block·next block →recent activity