pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,810,652
← previous block
next block →
recent activity
Analyzing
Block #94,810,652
11 transactions · 11 stateful · 2026-08-10 15:26:35 UTC
Parallelism
73
/100
Blocked
45
%
Avg conflicts / tx
0.64
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,810,652
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
#2
execOrder
· blocks 4
#5
0x3f5c179b
#8
transfer
· blocks 1
#10
setData
#3
execOrder
· blocks 1
#6
execFwdPositionOps
· blocks 1
#9
transfer
#4
execOrder
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
6
w1
7
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xfecb18c0…01ed
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcbe6eeba…6c8a
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
2 touches
0 conflicts
0x5a746750…e0fb
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
3 conflicts on slot
0xb3fb9fb561…7664db
Audit this contract →
← previous block
·
next block →
recent activity