pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,235,670
← previous block
next block →
recent activity
Analyzing
Block #94,235,670
11 transactions · 9 stateful · 2026-08-08 15:01:53 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,235,670
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
execOrders
#3
0x5acec890
· blocks 3
#6
execFwdPositionOps
#7
execute
#8
0x6a774559
#9
setData
#4
0x5acec890
#5
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x18ec97d9…6baa
0x34b655…2a6f
2 touches
0 conflicts
0x22c2bb0c…9d5d
0x34b655…2a6f
2 touches
0 conflicts
0x27a78688…b891
0x34b655…2a6f
2 touches
0 conflicts
0x2afe51f4…4006
0x34b655…2a6f
2 touches
0 conflicts
0x3d22c439…de6d
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
0x93b6fab01a…2d09d6
Audit this contract →
← previous block
·
next block →
recent activity