pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,538,412
← previous block
next block →
recent activity
Analyzing
Block #105,538,412
8 transactions · 8 stateful · 2026-09-17 06:51:20 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,538,412
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
transfer
#4
0x5acec890
· blocks 2
#7
0x59558d29
#5
0x5acec890
· blocks 1
#6
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5164ab0e…01e1
0xc8689a…ee79
6 touches
3 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0xb4b50f93…93e2
0x34b655…2a6f
6 touches
3 conflicts
0xb543d97e…cc3f
0x34b655…2a6f
6 touches
3 conflicts
0xc9d084aa…efb7
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0x2a8bc05a…0464
0x37db7f…ec7b
6 touches
3 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: Settlement / Helper
3 conflicts on slot
0x5164ab0e04…c201e1
Audit this contract →
← previous block
·
next block →
recent activity