← previous blocknext block →recent activity
Analyzing
Block #91,432,552
12 transactions · 11 stateful · 2026-07-29 19:56:18 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,432,552 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd33ebcd0…9f7e
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92115abd…ad76
0x34b655…2a6f
4 touches
1 conflict
0x0b1850d0…18b4
0x34b655…2a6f
2 touches
0 conflicts
0x0b2e78e5…1da8
0x34b655…2a6f
2 touches
0 conflicts
0x11a09e1c…bd50
0x34b655…2a6f
2 touches
0 conflicts
0x12df41b1…d03c
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 0xd33ebcd097…7e9f7e
Audit this contract →
← previous block·next block →recent activity