← previous blocknext block →recent activity
Analyzing
Block #91,419,444
16 transactions · 14 stateful · 2026-07-29 18:49:28 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,419,444 · 16 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
2w03w16w07w18w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfed09e59…a493
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0xb9854153…ac43
0x34b655…2a6f
4 touches
1 conflict
0x687a4940…fce9
0x34b655…2a6f
4 touches
1 conflict
0x191879d6…0917
0xd32edf…ff58
3 touches
1 conflict
0x3f4f9f22…8ad6
0x34b655…2a6f
2 touches
0 conflicts
0x3f4f9f22…8ad7
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 0xfed09e59c7…d6a493
Audit this contract →
← previous block·next block →recent activity