← previous blocknext block →recent activity
Analyzing
Block #86,341,336
24 transactions · 20 stateful · 2026-07-08 05:03:30 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,341,336 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w010w111w012w113w014w015w217w218w119w021w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87ee379a…cd9e
0x34b655…2a6f
10 touches
10 conflicts
0xda46a376…f6a6
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x608f0a83…9502
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x83539b28…24e0
0x34b655…2a6f
6 touches
3 conflicts
0x851ff3c1…1b15
0x34b655…2a6f
6 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: Perpl
10 conflicts on slot 0x87ee379aa1…d8cd9e
Audit this contract →
← previous block·next block →recent activity