pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,869,560
← previous block
next block →
recent activity
Analyzing
Block #94,869,560
9 transactions · 9 stateful · 2026-08-10 20:22:56 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,869,560
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
0x3f5c179b
#3
0x3f5c179b
#4
execFwdPositionOps
#5
setData
#6
execOrders
· blocks 1
#8
0x59558d29
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2a783bf…25e3
0x34b655…2a6f
4 touches
1 conflict
0xd145574b…436f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x010b6bfe…4581
0x34b655…2a6f
2 touches
0 conflicts
0x22aa142d…537b
0x34b655…2a6f
2 touches
0 conflicts
0x2a1544ad…9f70
0x34b655…2a6f
2 touches
0 conflicts
0x5f9b1c6b…cab0
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcc
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
0xc2a783bfdf…da25e3
Audit this contract →
← previous block
·
next block →
recent activity