pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,922,084
← previous block
next block →
recent activity
Analyzing
Block #93,922,084
8 transactions · 8 stateful · 2026-08-07 12:39:57 UTC
Parallelism
50
/100
Blocked
50
%
Avg conflicts / tx
0.88
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,922,084
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 3
#7
setData
#3
0x5acec890
· blocks 2
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa9fcbc7b…fa43
0x34b655…2a6f
6 touches
3 conflicts
0xfc3d5171…8357
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
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
6 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity