← previous blocknext block →recent activity
Analyzing
Block #87,489,405
24 transactions · 21 stateful · 2026-07-13 12:59:59 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,489,405 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w09w110w412w517w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82437f64…3f11
0x34b655…2a6f
8 touches
6 conflicts
0x521f03f8…dc0e
0x34b655…2a6f
8 touches
6 conflicts
0xe2c66a2e…150f
0x34b655…2a6f
6 touches
3 conflicts
0x22f5b72a…22e0
0x34b655…2a6f
6 touches
3 conflicts
0xdfe311f9…a651
0x34b655…2a6f
6 touches
3 conflicts
0x3f04840f…82ba
0x34b655…2a6f
4 touches
1 conflict
0x40e6ec54…fbf3
0x34b655…2a6f
4 touches
1 conflict
0x2976621e…4c88
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 0x82437f64ff…143f11
Audit this contract →
← previous block·next block →recent activity