← previous blocknext block →recent activity
Analyzing
Block #87,583,413
14 transactions · 13 stateful · 2026-07-13 23:29:34 UTC
Parallelism
50/100
Blocked
46%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,583,413 · 14 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
2w04w15w27w310w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8252706a…7ca5
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x829041ba…9a15
0x34b655…2a6f
6 touches
3 conflicts
0x36890fff…f3d1
0x34b655…2a6f
6 touches
3 conflicts
0x207b4a17…4084
0x34b655…2a6f
6 touches
3 conflicts
0x6b11b9de…f60a
0x34b655…2a6f
4 touches
1 conflict
0x75cb8e55…1cd9
0x34b655…2a6f
4 touches
1 conflict
0x8cd0745d…4dc0
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
15 conflicts on slot 0x8252706a8a…797ca5
Audit this contract →
← previous block·next block →recent activity