pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,300,157
← previous block
next block →
recent activity
Analyzing
Block #94,300,157
9 transactions · 9 stateful · 2026-08-08 20:28:36 UTC
Parallelism
67
/100
Blocked
44
%
Avg conflicts / tx
0.56
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,300,157
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 3
#4
placeAndExecuteMarketBuy
· blocks 1
#6
0x57368ddf
#8
setData
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#5
placeAndExecuteMarketBuy
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcf21e7a…acf1
0x34b655…2a6f
6 touches
3 conflicts
0x981b7617…6093
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8c39d2ab…756b
0xa6afd3…d132
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
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
3 conflicts on slot
0xbcf21e7a60…3facf1
Audit this contract →
← previous block
·
next block →
recent activity