← previous blocknext block →recent activity
Analyzing
Block #87,575,895
16 transactions · 16 stateful · 2026-07-13 22:39:16 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,575,895 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w08w19w110w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e17e5be…d212
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0xbc89da14…a1b5
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x560b6fd9…a104
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b8
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b9
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 0x5e17e5be17…c5d212
Audit this contract →
← previous block·next block →recent activity