← previous blocknext block →recent activity
Analyzing
Block #91,136,263
14 transactions · 14 stateful · 2026-07-28 19:03:27 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,136,263 · 14 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
2w03w04w16w17w28w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7be3246e…f89f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x6d955786…1327
0x34b655…2a6f
6 touches
3 conflicts
0xde284bf5…ab21
0x34b655…2a6f
6 touches
3 conflicts
0x004989aa…b35a
0x34b655…2a6f
6 touches
3 conflicts
0xa2cc9ea5…cac4
0x34b655…2a6f
4 touches
1 conflict
0xa6b48d6e…0705
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 0x7be3246e43…72f89f
Audit this contract →
← previous block·next block →recent activity