← previous blocknext block →recent activity
Analyzing
Block #91,136,274
20 transactions · 18 stateful · 2026-07-28 19:03:30 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,136,274 · 20 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
3w05w06w17w18w212w314w319w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x383e75cc…b79f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0x85c5eb6b…b05a
0x34b655…2a6f
4 touches
1 conflict
0x95dd1dda…bc0e
0x34b655…2a6f
4 touches
1 conflict
0xaccb4e7c…ee20
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
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 0x383e75ccf3…e9b79f
Audit this contract →
← previous block·next block →recent activity