← previous blocknext block →recent activity
Analyzing
Block #91,063,150
11 transactions · 11 stateful · 2026-07-28 12:55:34 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,063,150 · 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
4w05w06w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8a740d65…0429
0x34b655…2a6f
4 touches
1 conflict
0x8bddb6c6…c7b0
0x34b655…2a6f
4 touches
1 conflict
0x9a73834c…0f51
0x34b655…2a6f
4 touches
1 conflict
0x9a73834c…0f52
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 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity