pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,854,849
← previous block
next block →
recent activity
Analyzing
Block #93,854,849
11 transactions · 11 stateful · 2026-08-07 07:01:29 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,854,849
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
matchOrders
#5
0x57368ddf
#6
0x0f6795d9
#7
0x6a758340
#8
setData
#10
0xc7e3ec2c
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92115abd…ad76
0x34b655…2a6f
4 touches
1 conflict
0x08a39015…efa0
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x22bef947…cc48
0x34b655…2a6f
2 touches
0 conflicts
0x2f426d3b…7aa9
0x34b655…2a6f
2 touches
0 conflicts
0x399a45fd…1312
0x34b655…2a6f
2 touches
0 conflicts
0x42267eea…6c8b
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:
Perpl
1 conflict on slot
0x92115abda4…1fad76
Audit this contract →
← previous block
·
next block →
recent activity