pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,429,974
← previous block
next block →
recent activity
Analyzing
Block #106,429,974
11 transactions · 11 stateful · 2026-09-20 09:41:01 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,429,974
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
0x0c7abd22
#4
forward
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#7
execOrders
· blocks 1
#9
setData
#8
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w0
8
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0ad71078…339a
0x34b655…2a6f
2 touches
0 conflicts
0x108a6c85…c2b3
0x34b655…2a6f
2 touches
0 conflicts
0x12d85553…c183
0x34b655…2a6f
2 touches
0 conflicts
0x13932267…03bd
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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
0x1b25f26097…52c429
Audit this contract →
← previous block
·
next block →
recent activity