← previous blocknext block →recent activity
Analyzing
Block #86,313,324
19 transactions · 17 stateful · 2026-07-08 01:56:22 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,313,324 · 19 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
1w02w13w24w06w07w110w212w113w216w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98a1bad6…5130
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x3afcfe97…3b30
0x34b655…2a6f
6 touches
3 conflicts
0x459573ed…fbbe
0x34b655…2a6f
6 touches
3 conflicts
0x5cc231f5…f1cd
0x69df8a…6292
4 touches
1 conflict
0xb05cd4f5…73d0
0x69df8a…6292
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 0x98a1bad63b…2d5130
Audit this contract →
← previous block·next block →recent activity