← previous blocknext block →recent activity
Analyzing
Block #87,614,909
31 transactions · 26 stateful · 2026-07-14 03:00:11 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,614,909 · 31 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
3w04w08w09w110w213w115w216w217w319w123w226w030w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc514314c…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0x75b43fdd…8dc1
0x34b655…2a6f
4 touches
1 conflict
0x7d7ff6bb…f729
0x34b655…2a6f
4 touches
1 conflict
0x7e1c4eb9…198c
0x34b655…2a6f
4 touches
1 conflict
0x8bc8bc52…c222
0x34b655…2a6f
4 touches
1 conflict
0x91d48be7…e4e8
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity