← previous blocknext block →recent activity
Analyzing
Block #86,961,717
24 transactions · 23 stateful · 2026-07-11 02:11:50 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,961,717 · 24 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
2w03w14w05w111w212w115w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
6 touches
3 conflicts
0x86dfe00e…d800
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0x9d349109…9a69
0x34b655…2a6f
4 touches
1 conflict
0xa112f315…1a92
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity