← previous blocknext block →recent activity
Analyzing
Block #87,919,402
20 transactions · 17 stateful · 2026-07-15 12:56:51 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,919,402 · 20 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
1w02w14w05w16w09w110w011w214w315w419w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1952ceb…56be
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xb2e75fae…f11d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdd785f78…b5ea
0x34b655…2a6f
6 touches
3 conflicts
0xc6bb7e6c…bf35
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x56b5f5c0…a3ad
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 0xd1952ceb43…6456be
Audit this contract →
← previous block·next block →recent activity