← previous blocknext block →recent activity
Analyzing
Block #91,025,764
11 transactions · 11 stateful · 2026-07-28 09:47:29 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,025,764 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x434587c7…2645
0x34b655…2a6f
4 touches
1 conflict
0x2cc85280…c2f7
0x34b655…2a6f
2 touches
0 conflicts
0x48719cbe…5484
0x34b655…2a6f
2 touches
0 conflicts
0x560b6fd9…a104
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x93813fd8…2e96
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
6 conflicts on slot 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity