pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,978,814
← previous block
next block →
recent activity
Analyzing
Block #94,978,814
11 transactions · 8 stateful · 2026-08-11 05:32:24 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,978,814
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
· blocks 2
#3
executeBatch
#6
claim
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x32366535
#4
execFwdPositionOps
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x9adb2803…81f1
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0xe58009e8…fe3f
0x34b655…2a6f
4 touches
1 conflict
0x3107eccd…694b
0x34b655…2a6f
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
1 conflict on slot
0x8f2033941d…ebf2db
Audit this contract →
← previous block
·
next block →
recent activity