← previous blocknext block →recent activity
Analyzing
Block #86,318,627
23 transactions · 19 stateful · 2026-07-08 02:31:50 UTC
Parallelism
87/100
Blocked
37%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,318,627 · 23 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
3w04w15w26w17w210w011w112w013w114w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb05cd4f5…73d0
0x69df8a…6292
6 touches
3 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdb067026…9eb8
0x69df8a…6292
6 touches
3 conflicts
0x2545a5c0…75e0
0xd32edf…ff58
5 touches
3 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: 0x69df8a43…506292
3 conflicts on slot 0xb05cd4f5f9…f973d0
Audit this contract →
← previous block·next block →recent activity