← previous blocknext block →recent activity
Analyzing
Block #87,791,949
17 transactions · 16 stateful · 2026-07-14 22:44:24 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,791,949 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w09w012w113w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04a566e1…26f3
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x28c62bca…b746
0x34b655…2a6f
8 touches
6 conflicts
0x504befab…a991
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 touches
6 conflicts
0xcc6e2e88…6569
0x34b655…2a6f
8 touches
6 conflicts
0x8981596f…d14a
0x34b655…2a6f
7 touches
6 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
10 conflicts on slot 0x04a566e1fd…f826f3
Audit this contract →
← previous block·next block →recent activity