pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,752,221
← previous block
next block →
recent activity
Analyzing
Block #92,752,221
8 transactions · 8 stateful · 2026-08-03 10:35:16 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
#92,752,221
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
setData
#6
0x59558d29
#7
0xc7e3ec2c
#2
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca2926e0…61b5
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x63f544f5…174f
0x34b655…2a6f
3 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
2 touches
0 conflicts
0x266a6b2c…4377
0x34b655…2a6f
2 touches
0 conflicts
0x27b9caf2…c102
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
0x948836ff54…e859ab
Audit this contract →
← previous block
·
next block →
recent activity