pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,573,301
← previous block
next block →
recent activity
Analyzing
Block #95,573,301
11 transactions · 11 stateful · 2026-08-13 07:37:01 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,573,301
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
0x5acec890
#4
execFwdPositionOps
#5
0x3f5c179b
#6
0x57368ddf
#7
execFwdPositionOps
#8
forward
#9
setData
#3
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5090f250…2cb6
0x34b655…2a6f
4 touches
1 conflict
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0xf5c75a87…787c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x3efde171…60bb
0x34b655…2a6f
2 touches
0 conflicts
0x3f8289f2…18ff
0x34b655…2a6f
2 touches
0 conflicts
0x48a0f121…953b
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
0x5090f250f4…be2cb6
Audit this contract →
← previous block
·
next block →
recent activity