← previous blocknext block →recent activity
Analyzing
Block #91,904,257
10 transactions · 7 stateful · 2026-07-31 11:29:21 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,904,257 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e65daf1…ed48
0x34b655…2a6f
4 touches
1 conflict
0xb39cb1d8…effa
0x34b655…2a6f
4 touches
1 conflict
0x224d6800…4508
0x34b655…2a6f
2 touches
0 conflicts
0x23578a29…253c
0x34b655…2a6f
2 touches
0 conflicts
0x245dffcd…9fd4
0x34b655…2a6f
2 touches
0 conflicts
0x25a11da1…46af
0x34b655…2a6f
2 touches
0 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
2 touches
0 conflicts
0x35a09235…9aef
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
1 conflict on slot 0x4e65daf170…11ed48
Audit this contract →
← previous block·next block →recent activity