← previous blocknext block →recent activity
Analyzing
Block #87,627,884
13 transactions · 9 stateful · 2026-07-14 04:26:58 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,627,884 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x536588d3…19c5
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc4dc32ca…83f9
0x34b655…2a6f
4 touches
1 conflict
0xc4dc32ca…83fa
0x34b655…2a6f
4 touches
1 conflict
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x295faadc…ed75
0x34b655…2a6f
4 touches
1 conflict
0x2ea831bc…4b4c
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 0x536588d3d7…2719c5
Audit this contract →
← previous block·next block →recent activity