← previous blocknext block →recent activity
Analyzing
Block #87,586,692
20 transactions · 20 stateful · 2026-07-13 23:51:29 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,586,692 · 20 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
1w02w13w04w15w06w07w18w013w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc6c566e1…a6fa
0x34b655…2a6f
8 touches
6 conflicts
0xdf15e2bf…d7a9
0x34b655…2a6f
6 touches
3 conflicts
0x56f6adae…573c
0x34b655…2a6f
4 touches
1 conflict
0x5de95e2f…4c8f
0x34b655…2a6f
4 touches
1 conflict
0x7abe0396…ab27
0x34b655…2a6f
4 touches
1 conflict
0x7cd78950…607c
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity