pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,538,509
← previous block
next block →
recent activity
Analyzing
Block #92,538,509
9 transactions · 8 stateful · 2026-08-02 16:39:14 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,538,509
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
0x94defb17
#4
updateDataFeedsValuesPartial
#5
setData
#6
execOrders
#7
0x59558d29
· blocks 1
#3
execFwdPositionOps
#8
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x064a19b6…3f1d
0x34b655…2a6f
2 touches
0 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x1b49f420…7fe1
0x34b655…2a6f
2 touches
0 conflicts
0x20492d53…80f9
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
0xa56e54d018…f82d39
Audit this contract →
← previous block
·
next block →
recent activity