← previous blocknext block →recent activity
Analyzing
Block #87,587,741
19 transactions · 13 stateful · 2026-07-13 23:58:29 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,587,741 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w08w19w212w113w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5e6e5ee…9fb2
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x640530ff…86bc
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6736db11…0a95
0x34b655…2a6f
4 touches
1 conflict
0x7840c762…8060
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x89cb869a…08a6
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 0xd5e6e5eef3…f19fb2
Audit this contract →
← previous block·next block →recent activity