← previous blocknext block →recent activity
Analyzing
Block #91,279,987
10 transactions · 9 stateful · 2026-07-29 07:07:19 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,279,987 · 10 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xee9ef3c6…e901
0x34b655…2a6f
6 touches
3 conflicts
0xe40ce249…a28c
0x34b655…2a6f
6 touches
3 conflicts
0xed5337b6…cf51
0x34b655…2a6f
6 touches
3 conflicts
0x028f6095…b860
0x34b655…2a6f
4 touches
1 conflict
0x2d93071a…5ba7
0x34b655…2a6f
4 touches
1 conflict
0x4943c7e5…d013
0x34b655…2a6f
4 touches
1 conflict
0x4ec5ff53…d470
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