← previous blocknext block →recent activity
Analyzing
Block #86,943,260
20 transactions · 19 stateful · 2026-07-11 00:08:31 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,943,260 · 20 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
1w02w13w14w05w16w27w28w311w012w116w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x666b28db…11f0
0x34b655…2a6f
6 touches
3 conflicts
0x3b787279…727f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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