← previous blocknext block →recent activity
Analyzing
Block #91,444,468
10 transactions · 8 stateful · 2026-07-29 20:56:14 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,444,468 · 10 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
2w03w15w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x849c2133…33c6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xd70ab6b5…64cd
0x34b655…2a6f
4 touches
1 conflict
0x1a7f419a…6d58
0x34b655…2a6f
2 touches
0 conflicts
0x1f3da9ea…69c3
0x34b655…2a6f
2 touches
0 conflicts
0x35f935ff…bd20
0x34b655…2a6f
2 touches
0 conflicts
0x42ba766a…2659
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity