← previous blocknext block →recent activity
Analyzing
Block #91,437,592
29 transactions · 26 stateful · 2026-07-29 20:21:39 UTC
Parallelism
72/100
Blocked
58%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,437,592 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w08w09w110w211w314w315w316w417w420w423w524w625w726w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x92115abd…ad76
0x34b655…2a6f
8 touches
6 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
8 touches
6 conflicts
0x08636046…e60f
0x34b655…2a6f
8 touches
6 conflicts
0xa8cff7bf…d80f
0x34b655…2a6f
6 touches
3 conflicts
0xad065451…f5dd
0x34b655…2a6f
6 touches
3 conflicts
0xb1b21ea8…d790
0x34b655…2a6f
6 touches
3 conflicts
0xb2e75fae…f11d
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity