← previous blocknext block →recent activity
Analyzing
Block #91,097,197
31 transactions · 31 stateful · 2026-07-28 15:46:56 UTC
Parallelism
55/100
Blocked
65%
Avg conflicts / tx
2.45
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,097,197 · 31 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w18w29w110w211w312w413w514w615w716w817w918w1021w1122w1225w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x99701186…1cbf
0x34b655…2a6f
8 touches
6 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
8 touches
6 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x56a653f2…7434
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity