← previous blocknext block →recent activity
Analyzing
Block #86,214,742
28 transactions · 22 stateful · 2026-07-07 14:58:05 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,214,742 · 28 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
1w02w13w24w06w17w08w110w011w118w323w024w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xac5988bc…d15c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x4d3e58e0…a2d7
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
2 touches
0 conflicts
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