pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,576,011
← previous block
next block →
recent activity
Analyzing
Block #105,576,011
13 transactions · 11 stateful · 2026-09-17 10:00:34 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,576,011
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x5acec890
· blocks 2
#4
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
0x59558d29
#9
transfer
#10
batchUpdatePrice
#11
setData
#5
0x5acec890
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e632c…e14c
0x34b655…2a6f
6 touches
3 conflicts
0xd3d054d7…4bfb
0x37db7f…ec7b
4 touches
1 conflict
0xdad13823…6798
0x37db7f…ec7b
4 touches
1 conflict
0x1a6bdef5…144d
0x34b655…2a6f
4 touches
1 conflict
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0x3b65c5ca…9f83
0x34b655…2a6f
4 touches
1 conflict
0x75f36d60…8556
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xfd4e632c76…e1e14c
Audit this contract →
← previous block
·
next block →
recent activity