pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,646,488
← previous block
next block →
recent activity
Analyzing
Block #95,646,488
9 transactions · 9 stateful · 2026-08-13 13:45:09 UTC
Parallelism
44
/100
Blocked
56
%
Avg conflicts / tx
1
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,646,488
· 9 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
execOrder
· blocks 3
#7
transfer
#8
setData
#2
execOrder
#3
execOrder
· blocks 3
#4
execOrder
· blocks 2
#5
execOrder
· blocks 1
#6
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
4
w2
5
w3
6
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x2130f288…281f
0x34b655…2a6f
2 touches
0 conflicts
0x2bcdd4a1…3d3a
0x34b655…2a6f
2 touches
0 conflicts
0x3787c344…821f
0x34b655…2a6f
2 touches
0 conflicts
0x444eb03f…15d7
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
6 conflicts on slot
0xb3fb9fb561…7664db
Audit this contract →
← previous block
·
next block →
recent activity