pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,573,895
← previous block
next block →
recent activity
Analyzing
Block #105,573,895
10 transactions · 8 stateful · 2026-09-17 09:49:55 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,573,895
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x5acec890
· blocks 1
#5
0x59558d29
#6
execute
#7
0x3f5c179b
#8
setData
#9
execOrders
#4
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b7e5c4e…5fae
0x34b655…2a6f
4 touches
1 conflict
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0xb8acd6db…8581
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0xd3d054d7…4bfb
0x37db7f…ec7b
4 touches
1 conflict
0xdad13823…6798
0x37db7f…ec7b
4 touches
1 conflict
0x945d1dbe…e1d7
0xc8689a…ee79
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
1 conflict on slot
0x8b7e5c4e2c…845fae
Audit this contract →
← previous block
·
next block →
recent activity