← previous blocknext block →recent activity
Analyzing
Block #87,295,849
18 transactions · 17 stateful · 2026-07-12 15:25:41 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,295,849 · 18 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
1w02w13w24w39w010w111w212w113w214w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x48e6f054…d2ac
0x34b655…2a6f
4 touches
1 conflict
0x4940bb84…4ec2
0x34b655…2a6f
4 touches
1 conflict
0x4da61c94…532a
0x34b655…2a6f
4 touches
1 conflict
0x57f6fade…9347
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity