pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,977,850
← previous block
next block →
recent activity
Analyzing
Block #86,977,850
8 transactions · 5 stateful · 2026-07-11 03:59:34 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,977,850
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#7
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6a7552…a4b8
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b9
0x34b655…2a6f
4 touches
1 conflict
0x809b35f2…71ac
0x34b655…2a6f
4 touches
1 conflict
0x9debbac4…9a2a
0x34b655…2a6f
4 touches
1 conflict
0x3c4d27d3…1820
0x34b655…2a6f
4 touches
1 conflict
0xb5f244d5…f550
0x34b655…2a6f
4 touches
1 conflict
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xd1b40f29…9b9d
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
0x5b6a755253…30a4b8
Audit this contract →
← previous block
·
next block →
recent activity