pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,841,658
← previous block
next block →
recent activity
Analyzing
Block #94,841,658
8 transactions · 7 stateful · 2026-08-10 18:02:34 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,841,658
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 2
#4
execFwdPositionOps
#6
verifyOracleProofV2
#7
setData
#3
0x5acec890
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x26744466…9f4c
0x34b655…2a6f
2 touches
0 conflicts
0x4ef8d411…f9a0
0x34b655…2a6f
2 touches
0 conflicts
0x5b0ed476…61a6
0x34b655…2a6f
2 touches
0 conflicts
0x5c1e4658…3669
0x34b655…2a6f
2 touches
0 conflicts
0x78c8faa1…4d4a
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
3 conflicts on slot
0x840d3ab7c3…edc8c4
Audit this contract →
← previous block
·
next block →
recent activity