pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,472,489
← previous block
next block →
recent activity
Analyzing
Block #94,472,489
9 transactions · 8 stateful · 2026-08-09 11:04:14 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,472,489
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#5
batchUpdate
#6
0x6a785f25
#7
setData
#8
0xc7e3ec2c
#4
execFwdPositionOps
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
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x8660d71c…714d
0x34b655…2a6f
4 touches
1 conflict
0xc44810d5…a00a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x222733a8…8e7a
0x34b655…2a6f
2 touches
0 conflicts
0x222733a8…8e7b
0x34b655…2a6f
2 touches
0 conflicts
0x388a4c2f…9868
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
1 conflict on slot
0x20492d531d…7380f9
Audit this contract →
← previous block
·
next block →
recent activity