← previous blocknext block →recent activity
Analyzing
Block #91,105,567
10 transactions · 9 stateful · 2026-07-28 16:29:02 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,105,567 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382696ba…af63
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0x3accf018…2e8b
0x34b655…2a6f
4 touches
1 conflict
0x1b49f420…7fe1
0x34b655…2a6f
4 touches
1 conflict
0x92813843…c9cb
0x34b655…2a6f
4 touches
1 conflict
0xaccb4e7c…ee20
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 0x382696bafc…70af63
Audit this contract →
← previous block·next block →recent activity