← previous blocknext block →recent activity
Analyzing
Block #91,977,489
17 transactions · 14 stateful · 2026-07-31 17:37:42 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,977,489 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w29w310w412w513w614w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xff196840…a453
0x34b655…2a6f
8 touches
6 conflicts
0xd63ab65f…d79e
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
6 touches
3 conflicts
0x839be85f…a40b
0x34b655…2a6f
6 touches
3 conflicts
0x8aa29f68…5645
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity