← previous blocknext block →recent activity
Analyzing
Block #87,661,879
24 transactions · 20 stateful · 2026-07-14 08:14:06 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,661,879 · 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
1w02w13w04w18w19w210w311w412w515w016w617w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x3f7d8a09…362c
0x34b655…2a6f
6 touches
3 conflicts
0x28504822…ded6
0x34b655…2a6f
4 touches
1 conflict
0x342ae6d7…2e17
0x34b655…2a6f
4 touches
1 conflict
0x41d9a134…ccfe
0x34b655…2a6f
4 touches
1 conflict
0x454cdf57…aebc
0x34b655…2a6f
4 touches
1 conflict
0x560b6fd9…a104
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity