← previous blocknext block →recent activity
Analyzing
Block #87,791,841
9 transactions · 8 stateful · 2026-07-14 22:43:40 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,791,841 · 9 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
1w02w13w25w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04a566e1…26f3
0x34b655…2a6f
8 touches
6 conflicts
0x98834cc0…6c23
0x34b655…2a6f
6 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
6 touches
3 conflicts
0x46454bf3…6d84
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xb59b0c85…f36c
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x28c62bca…b746
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x04a566e1fd…f826f3
Audit this contract →
← previous block·next block →recent activity