← previous blocknext block →recent activity
Analyzing
Block #91,063,721
11 transactions · 10 stateful · 2026-07-28 12:58:26 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,063,721 · 11 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
2w03w16w07w18w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b5f80e5…d4a6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x10e72869…ab7f
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x57b02276…db3f
0x34b655…2a6f
4 touches
1 conflict
0x6b3c1134…cbf4
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 0x9b5f80e53e…2cd4a6
Audit this contract →
← previous block·next block →recent activity