← previous blocknext block →recent activity
Analyzing
Block #91,135,353
8 transactions · 7 stateful · 2026-07-28 18:58:52 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,135,353 · 8 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
1w02w04w15w06w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbc66586e…20fe
0x34b655…2a6f
6 touches
3 conflicts
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0x2f8f103b…29f4
0x34b655…2a6f
4 touches
1 conflict
0x42b04648…21d1
0x34b655…2a6f
4 touches
1 conflict
0x4d06828e…ad06
0x34b655…2a6f
4 touches
1 conflict
0x572969e1…311d
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity