pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,349,907
← previous block
next block →
recent activity
Analyzing
Block #86,349,907
11 transactions · 9 stateful · 2026-07-08 06:00:39 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,349,907
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x785f5745
#3
0x0f6795d9
#4
0x0f6795d9
#5
0x3f5c179b
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x39435dac
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x463017a2…d628
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0xd4ec0e7a…16df
0x0c65a0…0852
2 touches
0 conflicts
0x1ec685e6…eeec
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 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:
0x851145ea…9f3f07
1 conflict on slot
0x463017a20a…7cd628
Audit this contract →
← previous block
·
next block →
recent activity