pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,189,212
← previous block
next block →
recent activity
Analyzing
Block #106,189,212
13 transactions · 12 stateful · 2026-09-19 13:29:17 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,189,212
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x4297b034
#4
execOrder
· blocks 1
#6
0x5acec890
#7
0x5acec890
#8
0x59558d29
#9
setData
#10
resolveRound
#11
transfer
#12
0x6aae8e30
#5
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x1489eaf0…f00d
0x34b655…2a6f
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x4f858307…7642
0x34b655…2a6f
2 touches
0 conflicts
0x708d7a74…09e3
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
0xec7d120df9…5d7084
Audit this contract →
← previous block
·
next block →
recent activity