pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,848,228
← previous block
next block →
recent activity
Analyzing
Block #94,848,228
9 transactions · 9 stateful · 2026-08-10 18:35:38 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,848,228
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrder
#3
execOrders
· blocks 1
#5
execFwdPositionOps
#6
0x3f5c179b
#7
executeBatch
#8
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ce1ffed…4889
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x838ead73…d751
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
0x51c64da3…3b8c
0x34b655…2a6f
2 touches
0 conflicts
0x6743bc9f…1ed0
0x34b655…2a6f
2 touches
0 conflicts
0x67b7c4b9…179b
0x34b655…2a6f
2 touches
0 conflicts
0x6c429cc7…f975
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
0x8ce1ffed3d…764889
Audit this contract →
← previous block
·
next block →
recent activity