← previous blocknext block →recent activity
Analyzing
Block #91,278,703
7 transactions · 7 stateful · 2026-07-29 07:00:52 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,278,703 · 7 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb0221be…c2b3
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc2b37cdc…e470
0x34b655…2a6f
4 touches
1 conflict
0x046740ca…4065
0x34b655…2a6f
2 touches
0 conflicts
0x532d05cc…bff4
0x34b655…2a6f
2 touches
0 conflicts
0x7816acc8…173f
0x34b655…2a6f
2 touches
0 conflicts
0x9cf9008a…d826
0x34b655…2a6f
2 touches
0 conflicts
0xa6a26c30…d8c8
0x34b655…2a6f
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
3 conflicts on slot 0xcb0221bebc…d1c2b3
Audit this contract →
← previous block·next block →recent activity