pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,847,848
← previous block
next block →
recent activity
Analyzing
Block #104,847,848
10 transactions · 10 stateful · 2026-09-14 20:55:45 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,847,848
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
execOrders
· blocks 2
#6
execOrders
#7
setData
#8
execOrders
· blocks 1
#4
execOrders
· blocks 1
#9
execOrders
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0xf553d91c…8185
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x092e2a78…173f
0x34b655…2a6f
4 touches
1 conflict
0x9c168b41…7486
0x34b655…2a6f
4 touches
1 conflict
0x27fae18c…629a
0x34b655…2a6f
2 touches
0 conflicts
0x34ad8535…e1d3
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
3 conflicts on slot
0xbaf6ed88a9…dec179
Audit this contract →
← previous block
·
next block →
recent activity