← previous blocknext block →recent activity
Analyzing
Block #87,718,112
23 transactions · 15 stateful · 2026-07-14 14:30:28 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,718,112 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w19w010w114w115w216w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f234b05…db39
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0x51f60b9d…653f
0x34b655…2a6f
4 touches
1 conflict
0x56cb65af…855b
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x9354a4d0…be91
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
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
10 conflicts on slot 0x5f234b05a2…82db39
Audit this contract →
← previous block·next block →recent activity