pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,231,937
← previous block
next block →
recent activity
Analyzing
Block #94,231,937
13 transactions · 12 stateful · 2026-08-08 14:42:55 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,231,937
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#6
0x6a7740e7
#7
setData
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe464b77c…18d5
0x34b655…2a6f
4 touches
1 conflict
0x35c29640…8779
0x34b655…2a6f
4 touches
1 conflict
0x46db48f8…9bff
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x7281cd97…f967
0x34b655…2a6f
4 touches
1 conflict
0x91c78311…3b17
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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
0xe464b77ce3…5318d5
Audit this contract →
← previous block
·
next block →
recent activity