← previous blocknext block →recent activity
Analyzing
Block #91,069,812
16 transactions · 16 stateful · 2026-07-28 13:29:05 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,069,812 · 16 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
3w04w06w17w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63ac310a…f307
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xea6c2d78…6ac9
0x34b655…2a6f
5 touches
3 conflicts
0x65487580…b5eb
0x34b655…2a6f
5 touches
3 conflicts
0x4672a4ae…e965
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
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 0x63ac310ac6…37f307
Audit this contract →
← previous block·next block →recent activity