← previous blocknext block →recent activity
Analyzing
Block #87,713,633
12 transactions · 11 stateful · 2026-07-14 14:00:21 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,713,633 · 12 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
3w04w15w26w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x820b2f6b…9263
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xe06bbb2e…9417
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe06bbb2e…9416
0x34b655…2a6f
6 touches
3 conflicts
0x974c7a37…a6fe
0x34b655…2a6f
5 touches
3 conflicts
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xae2a51aa…6a06
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 0x820b2f6ba2…4d9263
Audit this contract →
← previous block·next block →recent activity