← previous blocknext block →recent activity
Analyzing
Block #87,787,568
20 transactions · 18 stateful · 2026-07-14 22:15:05 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,787,568 · 20 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
1w03w04w17w18w29w310w412w113w514w618w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd6e61f7…3ede
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x05a81321…6170
0x34b655…2a6f
6 touches
3 conflicts
0xa3c36de0…3cf3
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xefd93ead…49ac
0x34b655…2a6f
6 touches
3 conflicts
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 0xbd6e61f76f…523ede
Audit this contract →
← previous block·next block →recent activity