← previous blocknext block →recent activity
Analyzing
Block #91,104,217
19 transactions · 17 stateful · 2026-07-28 16:22:15 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,104,217 · 19 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
2w03w15w010w112w213w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3d22c439…de6d
0x34b655…2a6f
6 touches
3 conflicts
0xdbae25a9…d6f4
0x34b655…2a6f
6 touches
3 conflicts
0x6afd9468…c4a0
0x34b655…2a6f
6 touches
3 conflicts
0x59e89db7…661b
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
10 conflicts on slot 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity