← previous blocknext block →recent activity
Analyzing
Block #91,984,213
33 transactions · 33 stateful · 2026-07-31 18:11:31 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.7
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,984,213 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w37w49w510w611w612w713w816w120w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40cf21e3…e2c7
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xbdc80bf7…e947
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
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
21 conflicts on slot 0x40cf21e388…33e2c7
Audit this contract →
← previous block·next block →recent activity