pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,419,375
← previous block
next block →
recent activity
Analyzing
Block #92,419,375
7 transactions · 7 stateful · 2026-08-02 06:40:03 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,419,375
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 2
#4
execFwdPositionOps
#5
0x6a6ee6bb
#6
setData
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5f0304e…ed46
0x34b655…2a6f
6 touches
3 conflicts
0x26607bc2…7fd6
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3f2796bf…f0fa
0x34b655…2a6f
2 touches
0 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
2 touches
0 conflicts
0x4c619b7d…f4fa
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
3 conflicts on slot
0xd5f0304ef0…2eed46
Audit this contract →
← previous block
·
next block →
recent activity