pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,761,542
← previous block
next block →
recent activity
Analyzing
Block #93,761,542
12 transactions · 10 stateful · 2026-08-06 23:12:24 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,761,542
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x8263f5d9
#3
execOrders
#4
0x5acec890
· blocks 1
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
placeAndExecuteMarketBuy
#9
0xed82b078
#10
setData
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce3a759a…1620
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x4347b62a…ed5f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x159aac52…c583
0x34b655…2a6f
2 touches
0 conflicts
0x3e06ff9a…7489
0x34b655…2a6f
2 touches
0 conflicts
0x433ec3a1…a1e8
0x34b655…2a6f
2 touches
0 conflicts
0x444632f4…01f0
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
0xce3a759ab7…851620
Audit this contract →
← previous block
·
next block →
recent activity