← previous blocknext block →recent activity
Analyzing
Block #87,419,767
14 transactions · 13 stateful · 2026-07-13 05:14:24 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,419,767 · 14 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
2w03w04w15w06w27w38w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x4947e67f…aa39
0x34b655…2a6f
4 touches
1 conflict
0x4947e67f…aa3a
0x34b655…2a6f
4 touches
1 conflict
0x5b353877…605d
0x34b655…2a6f
4 touches
1 conflict
0x67d8b378…f2f8
0x34b655…2a6f
4 touches
1 conflict
0x6e27bdfb…108a
0x34b655…2a6f
4 touches
1 conflict
0x6f33580c…92d7
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity