pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,815,857
← previous block
next block →
recent activity
Analyzing
Block #94,815,857
12 transactions · 10 stateful · 2026-08-10 15:52:46 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,815,857
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
handleOps
#2
execOrder
· blocks 1
#3
execOrder
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
0x6a79f446
#8
transfer
#9
setData
#11
execOrders
#6
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0xa56a84d2…0dcd
0x000000…a032
2 touches
0 conflicts
0xb2449d1b…6994
0x000000…a032
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x27771b95…6161
0x34b655…2a6f
2 touches
0 conflicts
0x27c1af7d…e42a
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
0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block
·
next block →
recent activity