pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,581,557
← previous block
next block →
recent activity
Analyzing
Block #105,581,557
10 transactions · 10 stateful · 2026-09-17 10:28:29 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,581,557
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x5acec890
#4
0x5acec890
#5
0x5acec890
#6
0x59558d29
#7
setData
#8
0x3f5c179b
#9
0x6aabc0d0
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eb21bd9…aa8b
0x34b655…2a6f
4 touches
1 conflict
0x213b816c…a5e0
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x6805376a…fd45
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x439b7542…2f87
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x4df55aa1…e3d8
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
0x8eb21bd9c8…29aa8b
Audit this contract →
← previous block
·
next block →
recent activity