← previous blocknext block →recent activity
Analyzing
Block #91,126,804
12 transactions · 9 stateful · 2026-07-28 18:15:52 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,126,804 · 12 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
1w03w05w16w27w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc0e9c8…3ae6
0x34b655…2a6f
8 touches
6 conflicts
0xdb3f6210…2c83
0x34b655…2a6f
6 touches
3 conflicts
0xdd37452a…6190
0x34b655…2a6f
4 touches
1 conflict
0x2c66ecd1…f41d
0x34b655…2a6f
4 touches
1 conflict
0x418f6232…2de6
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
6 conflicts on slot 0x5cc0e9c8b0…1d3ae6
Audit this contract →
← previous block·next block →recent activity