← previous blocknext block →recent activity
Analyzing
Block #86,708,318
16 transactions · 13 stateful · 2026-07-09 21:58:15 UTC
Parallelism
75/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,708,318 · 16 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
1w06w17w011w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98b248c3…9ea5
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0xfcaee83d…428d
0x34b655…2a6f
4 touches
1 conflict
0x93701943…012b
0x34b655…2a6f
4 touches
1 conflict
0xb815046f…4859
0x34b655…2a6f
4 touches
1 conflict
0xc6d08d8c…2b98
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
3 conflicts on slot 0x98b248c323…8e9ea5
Audit this contract →
← previous block·next block →recent activity