pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,676,093
← previous block
next block →
recent activity
Analyzing
Block #94,676,093
9 transactions · 7 stateful · 2026-08-10 04:08:16 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,676,093
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
0x3f5c179b
#4
forward
#5
updateDataFeedsValuesPartial
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x56b75a1a…340c
0x34b655…2a6f
4 touches
1 conflict
0xe66201d4…84f1
0x34b655…2a6f
4 touches
1 conflict
0x2cc85280…c2f7
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f3
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f4
0x34b655…2a6f
2 touches
0 conflicts
0x47499bd7…58cd
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
0x91cdfdebc5…487feb
Audit this contract →
← previous block
·
next block →
recent activity