← previous blocknext block →recent activity
Analyzing
Block #87,662,913
23 transactions · 22 stateful · 2026-07-14 08:21:01 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,662,913 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w19w010w111w214w315w416w520w222w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6ed530e…fa7d
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x991c9324…f937
0xd32edf…ff58
5 touches
3 conflicts
0x10fec71b…e12f
0x34b655…2a6f
4 touches
1 conflict
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x1ae78ca0…5cca
0x34b655…2a6f
4 touches
1 conflict
0x1b8d60c6…dddc
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
6 conflicts on slot 0xc6ed530ecc…a9fa7d
Audit this contract →
← previous block·next block →recent activity