pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#111,847,803
← previous block
next block →
recent activity
Analyzing
Block #111,847,803
13 transactions · 13 stateful · 2026-10-09 08:24:49 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#111,847,803
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x00040000
#2
0x000025ee
#3
0x32d01e04
#4
setData
#5
0x59558d29
#6
execOrders
#7
updatePrices
#8
0x3f5c179b
#9
0x0c7abd22
#10
execFwdPositionOpsV2
#11
0x61d59c2d
· blocks 1
#12
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c6
0x508254…98bd
4 touches
1 conflict
0x46344427…7f31
0x508254…98bd
4 touches
1 conflict
0x4ea2b33b…7dbc
0x508254…98bd
4 touches
1 conflict
0x6c04daad…1130
0x508254…98bd
4 touches
1 conflict
0xcc69885f…792f
0x30a88b…7102
2 touches
0 conflicts
0xd5d6c8dc…8045
0x30a88b…7102
2 touches
0 conflicts
0xd9d16d34…330f
0x30a88b…7102
2 touches
0 conflicts
0xdc686ec4…237e
0x30a88b…7102
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:
0x508254c8…4a98bd
1 conflict on slot
0x3a663e9a3a…2fa9c6
Audit this contract →
← previous block
·
next block →
recent activity