← previous blocknext block →recent activity
Analyzing
Block #87,577,060
15 transactions · 14 stateful · 2026-07-13 22:47:03 UTC
Parallelism
47/100
Blocked
50%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,577,060 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w48w59w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0xc36fa358…24cb
0x34b655…2a6f
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0xe2607c11…8fa7
0x34b655…2a6f
6 touches
3 conflicts
0x44fdb4b6…2ce4
0x34b655…2a6f
4 touches
1 conflict
0x44fdb4b6…2ce5
0x34b655…2a6f
4 touches
1 conflict
0x4d73f502…968b
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
28 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity