← previous blocknext block →recent activity
Analyzing
Block #87,593,413
31 transactions · 26 stateful · 2026-07-14 00:36:26 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,593,413 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w010w111w212w315w018w222w025w227w328w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4467ecee…e95b
0x34b655…2a6f
8 touches
6 conflicts
0x83d11cdf…4b92
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xf71d9ad5…1d26
0x34b655…2a6f
6 touches
3 conflicts
0x3f85f288…7c97
0x34b655…2a6f
6 touches
3 conflicts
0x4cf1ac8e…5ecf
0x34b655…2a6f
6 touches
3 conflicts
0x9863393c…ce7b
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x4467eceedf…bfe95b
Audit this contract →
← previous block·next block →recent activity