← previous blocknext block →recent activity
Analyzing
Block #91,997,157
15 transactions · 13 stateful · 2026-07-31 19:16:38 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,997,157 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w29w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5427efe9…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x051aa260…b0a4
0x34b655…2a6f
4 touches
1 conflict
0xde95b18d…3751
0x34b655…2a6f
4 touches
1 conflict
0x20317244…edb4
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bb0bfb0…8f11
0x34b655…2a6f
4 touches
1 conflict
0x9cc81330…2fcf
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
3 conflicts on slot 0x5427efe953…12f9f3
Audit this contract →
← previous block·next block →recent activity