← previous blocknext block →recent activity
Analyzing
Block #91,008,631
9 transactions · 9 stateful · 2026-07-28 08:21:09 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,008,631 · 9 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
1w02w13w25w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe64d2555…8caf
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0x21280422…0930
0x34b655…2a6f
4 touches
1 conflict
0x60e002ca…bfd2
0x34b655…2a6f
2 touches
0 conflicts
0x6254804c…a03b
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
3 conflicts on slot 0xe64d255503…c58caf
Audit this contract →
← previous block·next block →recent activity