← previous blocknext block →recent activity
Analyzing
Block #91,985,093
13 transactions · 11 stateful · 2026-07-31 18:15:57 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,985,093 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x849c2133…33c6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd91d0474…123d
0x34b655…2a6f
4 touches
1 conflict
0x3236b41e…656c
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x3b60f2a7…e0fc
0x34b655…2a6f
2 touches
0 conflicts
0x521a91b0…b4c9
0x34b655…2a6f
2 touches
0 conflicts
0x543e16f7…48ac
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x849c21338c…9f33c6
Audit this contract →
← previous block·next block →recent activity