← previous blocknext block →recent activity
Analyzing
Block #91,104,233
23 transactions · 19 stateful · 2026-07-28 16:22:20 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,104,233 · 23 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
1w02w13w06w18w214w215w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xff3d6184…43dd
0x34b655…2a6f
6 touches
3 conflicts
0x6e7b64d9…062e
0x34b655…2a6f
6 touches
3 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x2d3930d3…c9b8
0x34b655…2a6f
4 touches
1 conflict
0x421099c9…8896
0x34b655…2a6f
4 touches
1 conflict
0x4ebc912e…ddb7
0x34b655…2a6f
4 touches
1 conflict
0x65487580…b5eb
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity