← previous blocknext block →recent activity
Analyzing
Block #91,132,292
6 transactions · 6 stateful · 2026-07-28 18:43:28 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,132,292 · 6 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7d
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7e
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0xd9d0b0b5…32f5
0x34b655…2a6f
3 touches
1 conflict
0xedbcc1e9…6452
0x34b655…2a6f
3 touches
1 conflict
0x55a1d3ef…36bf
0x34b655…2a6f
2 touches
0 conflicts
0x65c4f43b…0471
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 0xa779293bef…815e59
Audit this contract →
← previous block·next block →recent activity