← previous blocknext block →recent activity
Analyzing
Block #91,130,830
18 transactions · 16 stateful · 2026-07-28 18:36:07 UTC
Parallelism
61/100
Blocked
44%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,130,830 · 18 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
3w05w06w07w18w29w310w411w512w617w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd22dd5e8…83ff
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x418f6232…2de6
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa779293b…5e59
0x34b655…2a6f
8 touches
6 conflicts
0xb8a17327…4cec
0x34b655…2a6f
8 touches
6 conflicts
0xbc914adb…79c1
0x34b655…2a6f
6 touches
3 conflicts
0x65977bc0…2640
0x34b655…2a6f
6 touches
3 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 0xd22dd5e874…5383ff
Audit this contract →
← previous block·next block →recent activity