← previous blocknext block →recent activity
Analyzing
Block #91,957,188
20 transactions · 18 stateful · 2026-07-31 15:55:36 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,957,188 · 20 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
1w06w17w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff6d7c65…a5c7
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0x991e2e20…94a6
0x34b655…2a6f
4 touches
1 conflict
0xd5c98027…9fd9
0x34b655…2a6f
4 touches
1 conflict
0x78d51787…761a
0x34b655…2a6f
2 touches
0 conflicts
0x7c1d804e…835c
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 0xff6d7c65a2…c7a5c7
Audit this contract →
← previous block·next block →recent activity