pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,849,067
← previous block
next block →
recent activity
Analyzing
Block #94,849,067
9 transactions · 9 stateful · 2026-08-10 18:39:51 UTC
Parallelism
56
/100
Blocked
44
%
Avg conflicts / tx
1
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,849,067
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrder
· blocks 4
#2
execOrders
#7
0x30a19e01
#8
setData
#3
execOrders
· blocks 3
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w3
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b1b086a…4542
0x34b655…2a6f
8 touches
6 conflicts
0xa2cc9ea5…cac4
0x34b655…2a6f
8 touches
6 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
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:
Perpl
6 conflicts on slot
0x1b1b086af0…3c4542
Audit this contract →
← previous block
·
next block →
recent activity