← previous blocknext block →recent activity
Analyzing
Block #87,761,335
20 transactions · 19 stateful · 2026-07-14 19:19:34 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,761,335 · 20 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
2w03w05w16w27w38w412w113w214w315w416w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xa55c4598…2988
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x28c62bca…b746
0x34b655…2a6f
8 touches
6 conflicts
0x5adde4e4…73c9
0x34b655…2a6f
8 touches
6 conflicts
0x747f609d…1555
0x34b655…2a6f
8 touches
6 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity