← previous blocknext block →recent activity
Analyzing
Block #87,588,881
32 transactions · 30 stateful · 2026-07-14 00:06:07 UTC
Parallelism
47/100
Blocked
70%
Avg conflicts / tx
4.75
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,588,881 · 32 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w07w18w29w310w411w512w613w714w815w916w1017w1118w1221w127w1228w1329w1430w1531w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd93edb3f…94ec
0x34b655…2a6f
30 touches
105 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x34d95d94…3a16
0x34b655…2a6f
24 touches
66 conflicts
0x201679bc…0414
0x34b655…2a6f
24 touches
66 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
24 touches
66 conflicts
0x875164c2…f8a2
0x34b655…2a6f
24 touches
66 conflicts
0x9fd37234…2731
0x34b655…2a6f
24 touches
66 conflicts
0xa24365bc…5064
0x34b655…2a6f
24 touches
66 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
105 conflicts on slot 0xd93edb3f20…0394ec
Audit this contract →
← previous block·next block →recent activity