pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,816,635
← previous block
next block →
recent activity
Analyzing
Block #94,816,635
8 transactions · 8 stateful · 2026-08-10 15:56:41 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,816,635
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x3f5c179b
#3
executeBatch
· blocks 1
#5
execFwdPositionOps
#6
setData
#7
execOrders
#4
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xf658315c…b5cc
0xe52b14…7230
3 touches
1 conflict
0x0b82a929…9a58
0x34b655…2a6f
2 touches
0 conflicts
0x1404b00b…d8b3
0x34b655…2a6f
2 touches
0 conflicts
0x3b689fd2…629c
0x34b655…2a6f
2 touches
0 conflicts
0x3cb07f3b…6e72
0x34b655…2a6f
2 touches
0 conflicts
0x4acbdbcf…a8c6
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:
0xe52b1424…bb7230
1 conflict on slot
0x8ffa332881…c9ce11
Audit this contract →
← previous block
·
next block →
recent activity