pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,757,591
← previous block
next block →
recent activity
Analyzing
Block #92,757,591
11 transactions · 11 stateful · 2026-08-03 11:02:17 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,757,591
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xb2d4797b
#5
0x0f6795d9
· blocks 1
#7
relay
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#2
matchOrders
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5316d608…249e
0x99c7a7…8bf0
4 touches
1 conflict
0x04ab5947…620f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2653015d…fe7b
0x754704…b603
4 touches
1 conflict
0x7ecd788b…5190
0x754704…b603
4 touches
1 conflict
0xb7b1101c…2e93
0x754704…b603
4 touches
1 conflict
0x0534080b…baff
0x99c7a7…8bf0
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x5316d60877…c6249e
Audit this contract →
← previous block
·
next block →
recent activity