← previous blocknext block →recent activity
Analyzing
Block #91,110,496
35 transactions · 26 stateful · 2026-07-28 16:53:50 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,110,496 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w210w311w012w113w214w315w419w120w221w122w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x32626666…080c
0x34b655…2a6f
4 touches
1 conflict
0x4465a1e3…8878
0x34b655…2a6f
4 touches
1 conflict
0x640b61a9…cda9
0x34b655…2a6f
4 touches
1 conflict
0x99701186…1cbf
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity