← previous blocknext block →recent activity
Analyzing
Block #87,910,012
21 transactions · 17 stateful · 2026-07-15 11:54:04 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,910,012 · 21 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
4w07w110w011w112w214w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf28cf8dc…b0ca
0x34b655…2a6f
8 touches
6 conflicts
0xa745dbb2…a3a1
0x34b655…2a6f
6 touches
3 conflicts
0x36077f58…66cd
0x34b655…2a6f
4 touches
1 conflict
0x3802e15c…5960
0x34b655…2a6f
4 touches
1 conflict
0x3b63666d…e4f6
0x34b655…2a6f
4 touches
1 conflict
0x3b63666d…e4f7
0x34b655…2a6f
4 touches
1 conflict
0x3f7d8a09…362c
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
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
6 conflicts on slot 0xf28cf8dcba…4ab0ca
Audit this contract →
← previous block·next block →recent activity