← previous blocknext block →recent activity
Analyzing
Block #87,616,486
21 transactions · 18 stateful · 2026-07-14 03:10:44 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,616,486 · 21 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
1w02w13w04w15w06w19w010w011w212w115w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb6b7c45d…9d5a
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x0caac81d…a6f7
0x34b655…2a6f
4 touches
1 conflict
0x0ec126c8…5104
0x34b655…2a6f
4 touches
1 conflict
0x101e6777…e7a9
0x34b655…2a6f
4 touches
1 conflict
0x117cb8ea…a1dc
0x34b655…2a6f
4 touches
1 conflict
0x13031383…b239
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity