pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,312,591
← previous block
next block →
recent activity
Analyzing
Block #92,312,591
9 transactions · 9 stateful · 2026-08-01 21:43:04 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,312,591
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
0x3f5c179b
#3
0x94defb17
· blocks 1
#6
setData
#7
0x59558d29
#8
0xc7e3ec2c
#4
0x94defb17
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9aa906b…7bcd
0x7b9256…1fb2
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x3c06bc75…0c10
0x7b9256…1fb2
4 touches
1 conflict
0x3c06bc75…0c11
0x7b9256…1fb2
4 touches
1 conflict
0xc9aa906b…7bc9
0x7b9256…1fb2
4 touches
1 conflict
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:
0x7b9256fd…e21fb2
1 conflict on slot
0xc9aa906b32…327bcd
Audit this contract →
← previous block
·
next block →
recent activity