← previous blocknext block →recent activity
Analyzing
Block #87,642,988
24 transactions · 19 stateful · 2026-07-14 06:07:53 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,642,988 · 24 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
2w03w14w05w16w213w014w115w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xfdd655b8…bf89
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x78b7945b…2113
0x34b655…2a6f
6 touches
3 conflicts
0x347e379a…e2ba
0xd32edf…ff58
5 touches
3 conflicts
0x435b08b5…d84e
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x220a8541…6431
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity