← previous blocknext block →recent activity
Analyzing
Block #87,714,611
20 transactions · 16 stateful · 2026-07-14 14:06:55 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,714,611 · 20 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
1w02w13w04w18w09w110w211w313w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1bc07c63…d6ad
0x34b655…2a6f
4 touches
1 conflict
0x1f9a8e7a…8d21
0x34b655…2a6f
4 touches
1 conflict
0x572f121e…964f
0x34b655…2a6f
4 touches
1 conflict
0x5932b8f8…945d
0x34b655…2a6f
4 touches
1 conflict
0x7ae44958…8593
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity