pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,223,937
← previous block
next block →
recent activity
Analyzing
Block #92,223,937
9 transactions · 9 stateful · 2026-08-01 14:17:10 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,223,937
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#4
handleOps
#5
0x8b80a919
#6
setData
#7
0x59558d29
#8
0xc7e3ec2c
#2
execFwdPositionOps
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13fa8d63…ba0d
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1658
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1659
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
2 touches
0 conflicts
0x3e412550…5c60
0x34b655…2a6f
2 touches
0 conflicts
0x42b10c57…3ee7
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
0x13fa8d637b…d7ba0d
Audit this contract →
← previous block
·
next block →
recent activity