← previous blocknext block →recent activity
Analyzing
Block #91,981,927
37 transactions · 31 stateful · 2026-07-31 18:00:01 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,981,927 · 37 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w011w112w215w219w428w029w132w033w334w035w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x521a91b0…b4c9
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0x794ca895…607d
0x34b655…2a6f
4 touches
1 conflict
0x06fe3e5b…587d
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity