← previous blocknext block →recent activity
Analyzing
Block #86,831,248
16 transactions · 12 stateful · 2026-07-10 11:39:43 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,831,248 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bd6ddeb…9a19
0x34b655…2a6f
4 touches
1 conflict
0x6f4bb7f8…ac41
0x34b655…2a6f
4 touches
1 conflict
0xbd378a81…86fa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5c
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5d
0x34b655…2a6f
4 touches
1 conflict
0xd90f5e83…65f1
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
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
1 conflict on slot 0x1bd6ddeb70…259a19
Audit this contract →
← previous block·next block →recent activity