pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,471,688
← previous block
next block →
recent activity
Analyzing
Block #94,471,688
12 transactions · 9 stateful · 2026-08-09 11:00:09 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,471,688
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
· blocks 1
#4
0x5acec890
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
execOrders
#10
setData
#11
0xc7e3ec2c
#3
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1338b9e5…b467
0x065c9d…c394
2 touches
0 conflicts
0x32755283…ef11
0x065c9d…c394
2 touches
0 conflicts
0x39a3af41…8d99
0x065c9d…c394
2 touches
0 conflicts
0x6e9cc4cc…f639
0x065c9d…c394
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity