pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,999,975
← previous block
next block →
recent activity
Analyzing
Block #94,999,975
10 transactions · 10 stateful · 2026-08-11 07:18:50 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,999,975
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 2
#2
0x5acec890
#5
repayWithCollateral
#6
placeAndExecuteMarketBuy
#7
handleOps
#8
setData
#9
0x59558d29
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x11027baf…6ac3
0x34b655…2a6f
4 touches
1 conflict
0x02f5fbf9…5918
0x34b655…2a6f
2 touches
0 conflicts
0x153d1e25…10ea
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x8c1b3662…8075
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
0x261cbea79d…12e35e
Audit this contract →
← previous block
·
next block →
recent activity