← previous blocknext block →recent activity
Analyzing
Block #87,595,550
16 transactions · 12 stateful · 2026-07-14 00:50:44 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,595,550 · 16 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
5w06w17w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0x1f40ac22…24cb
0x34b655…2a6f
4 touches
1 conflict
0x3d10254d…8226
0x34b655…2a6f
4 touches
1 conflict
0x4fe04d4c…5a89
0x34b655…2a6f
4 touches
1 conflict
0x6b259aa9…cfba
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity