pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,821,350
← previous block
next block →
recent activity
Analyzing
Block #85,821,350
11 transactions · 8 stateful · 2026-07-05 19:13:27 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,821,350
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6e060c2c
#2
updateDataFeedsValuesPartial
#3
0x785f5745
#4
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#7
setData
#8
0xa25200…7879
#9
0x36365e…43b9
#10
0x39435dac
#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
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0xdf557d7f…49dd
0x0c65a0…0852
2 touches
0 conflicts
0x3a3e30bd…29eb
0x34b655…2a6f
2 touches
0 conflicts
0x5588d596…55d9
0x34b655…2a6f
2 touches
0 conflicts
0x2734e00b…9b4f
0x3bd359…433a
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:
Perpl
1 conflict on slot
0xda2ee2e777…e7968a
Audit this contract →
← previous block
·
next block →
recent activity