← previous blocknext block →recent activity
Analyzing
Block #91,190,186
13 transactions · 12 stateful · 2026-07-28 23:34:43 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,190,186 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w37w48w512w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e689c48…a06b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1526b11f…8b21
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x65977bc0…2640
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x8b2e4303…b36c
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
6 conflicts on slot 0x6e689c4879…c8a06b
Audit this contract →
← previous block·next block →recent activity