← previous blocknext block →recent activity
Analyzing
Block #91,099,753
13 transactions · 12 stateful · 2026-07-28 15:59:48 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,099,753 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xfbcd1a83…7b19
0x34b655…2a6f
4 touches
1 conflict
0x0b16c8b6…7b05
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe2263bea…6a9e
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6a9f
0x2b46c0…1669
2 touches
0 conflicts
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
1 conflict on slot 0x641aed075a…00bcb9
Audit this contract →
← previous block·next block →recent activity