← previous blocknext block →recent activity
Analyzing
Block #87,263,303
15 transactions · 14 stateful · 2026-07-12 11:48:03 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,263,303 · 15 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
1w02w13w04w17w28w39w411w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x0a5a4598…01bc
0x34b655…2a6f
4 touches
1 conflict
0x1353affc…75e0
0x34b655…2a6f
4 touches
1 conflict
0x3ad88d63…14c2
0x34b655…2a6f
4 touches
1 conflict
0x46199690…6fff
0x34b655…2a6f
4 touches
1 conflict
0x57c3fa9e…daa7
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity