pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,542,433
← previous block
next block →
recent activity
Analyzing
Block #92,542,433
11 transactions · 10 stateful · 2026-08-02 16:58:58 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,542,433
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketBuy
· blocks 1
#6
setData
#7
execOrders
#8
0x59558d29
· blocks 1
#10
0xc7e3ec2c
#5
batchUpdate
#9
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x08dc39c7…0d58
0x40c49f…2af0
3 touches
1 conflict
0x23361cbc…b058
0x34b655…2a6f
2 touches
0 conflicts
0x4565f421…80b9
0x34b655…2a6f
2 touches
0 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
2 touches
0 conflicts
0x803eb45d…00bd
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004c
Audit this contract →
← previous block
·
next block →
recent activity