← previous blocknext block →recent activity
Analyzing
Block #91,294,281
16 transactions · 15 stateful · 2026-07-29 08:19:15 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,294,281 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w19w010w111w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x63ce9942…9c7e
0xd32edf…ff58
5 touches
3 conflicts
0x0b26b03e…ecb6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x87a24499…0acf
0x34b655…2a6f
4 touches
1 conflict
0x87a24499…0ad0
0x34b655…2a6f
4 touches
1 conflict
0xa36ebe91…7256
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity