← previous blocknext block →recent activity
Analyzing
Block #87,718,097
18 transactions · 16 stateful · 2026-07-14 14:30:22 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,718,097 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w28w39w410w511w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f234b05…db39
0x34b655…2a6f
6 touches
3 conflicts
0xd770071c…467d
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x0a471d54…47c4
0x34b655…2a6f
4 touches
1 conflict
0x0ea46b1d…c9a4
0x34b655…2a6f
4 touches
1 conflict
0x20317244…edb4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x24d58d14…f7a5
0x34b655…2a6f
4 touches
1 conflict
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 0x5f234b05a2…82db39
Audit this contract →
← previous block·next block →recent activity