← previous blocknext block →recent activity
Analyzing
Block #91,418,210
21 transactions · 18 stateful · 2026-07-29 18:43:15 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,418,210 · 21 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
1w02w13w27w08w19w210w211w314w415w318w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x496e2285…b499
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3dc8ed8f…9df1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x641aed07…bcb9
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 0x496e228536…b4b499
Audit this contract →
← previous block·next block →recent activity