pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,905,229
← previous block
next block →
recent activity
Analyzing
Block #91,905,229
9 transactions · 8 stateful · 2026-07-31 11:34:14 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,905,229
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
0x3f5c179b
#4
execFwdPositionOps
· blocks 1
#6
0x6a6c88ae
#7
setData
#8
0x59558d29
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x78541caf…bfec
0x34b655…2a6f
4 touches
1 conflict
0x9efbd42c…c1bb
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…5990
0x34b655…2a6f
2 touches
0 conflicts
0x5ec20bc2…fafa
0x34b655…2a6f
2 touches
0 conflicts
0x68caa37b…c795
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity