← previous blocknext block →recent activity
Analyzing
Block #87,585,885
23 transactions · 19 stateful · 2026-07-13 23:46:05 UTC
Parallelism
78/100
Blocked
37%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,585,885 · 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
1w02w13w04w06w17w211w112w213w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2453506…54e4
0x34b655…2a6f
6 touches
3 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0x2e64e234…5cfa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4fc141d9…bb37
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xd2453506e1…f954e4
Audit this contract →
← previous block·next block →recent activity