← previous blocknext block →recent activity
Analyzing
Block #91,291,338
16 transactions · 16 stateful · 2026-07-29 08:04:27 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,291,338 · 16 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
1w02w13w04w16w27w28w39w411w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac8a5059…fd42
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0xfdd0bcbf…ee0a
0x34b655…2a6f
6 touches
3 conflicts
0x30223017…fddf
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
10 conflicts on slot 0xac8a5059ab…e9fd42
Audit this contract →
← previous block·next block →recent activity