← previous blocknext block →recent activity
Analyzing
Block #87,616,372
22 transactions · 17 stateful · 2026-07-14 03:09:58 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,616,372 · 22 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
1w02w14w05w16w27w38w410w111w212w113w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64687417…8d60
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x2c53a187…3646
0x34b655…2a6f
6 touches
3 conflicts
0x68b75835…d6f3
0x34b655…2a6f
6 touches
3 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
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 0x64687417b8…b08d60
Audit this contract →
← previous block·next block →recent activity