← previous blocknext block →recent activity
Analyzing
Block #91,126,421
12 transactions · 11 stateful · 2026-07-28 18:13:57 UTC
Parallelism
58/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,126,421 · 12 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
1w03w04w16w27w18w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93ce58d1…a6fa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa779293b…5e59
0x34b655…2a6f
6 touches
3 conflicts
0x42578f4c…5779
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x93ce58d128…94a6fa
Audit this contract →
← previous block·next block →recent activity