← previous blocknext block →recent activity
Analyzing
Block #86,387,147
35 transactions · 33 stateful · 2026-07-08 10:09:39 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.11
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,387,147 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w08w310w011w114w315w016w117w218w421w122w428w629w731w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
10 touches
10 conflicts
0xb75667b3…3080
0xd32edf…ff58
9 touches
10 conflicts
0x7a6681a8…c81c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x5f251b96…6054
0x34b655…2a6f
6 touches
3 conflicts
0x7cee1be1…e770
0x34b655…2a6f
6 touches
3 conflicts
0x8cce569d…1a6b
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 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity