pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,394,718
← previous block
next block →
recent activity
Analyzing
Block #108,394,718
10 transactions · 9 stateful · 2026-09-27 06:33:21 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,394,718
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0xab083028
#3
0xe10c815c
#4
execute
#5
0x84403c1b
· blocks 1
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#6
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2374606…93f7
0x34b655…2a6f
4 touches
1 conflict
0x87b3c188…6ea2
0x34b655…2a6f
4 touches
1 conflict
0xf1b18a92…23de
0x34b655…2a6f
4 touches
1 conflict
0x908b3417…88d2
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
2 touches
0 conflicts
0x35f4edc5…0b21
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0xc23746066e…f193f7
Audit this contract →
← previous block
·
next block →
recent activity