← previous blocknext block →recent activity
Analyzing
Block #87,664,527
27 transactions · 20 stateful · 2026-07-14 08:31:49 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,664,527 · 27 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
1w03w04w15w06w115w016w117w218w319w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb092633…b7c1
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0xe6e9c8e6…bc0c
0x34b655…2a6f
6 touches
3 conflicts
0x4e86f6b3…99b7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
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 0xfb092633f6…e5b7c1
Audit this contract →
← previous block·next block →recent activity