← previous blocknext block →recent activity
Analyzing
Block #87,920,730
27 transactions · 22 stateful · 2026-07-15 13:05:45 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,920,730 · 27 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
1w07w010w111w213w014w115w316w419w020w121w125w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6689d73a…ba50
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc1a44382…f1ca
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x6e171c1f…05b7
0x34b655…2a6f
4 touches
1 conflict
0x731f2745…9370
0xa6afd3…d132
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 0x6689d73aac…09ba50
Audit this contract →
← previous block·next block →recent activity