pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,611,501
← previous block
next block →
recent activity
Analyzing
Block #112,611,501
10 transactions · 8 stateful · 2026-10-12 00:27:16 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
#112,611,501
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9ac0761c
· blocks 1
#3
0x59558d29
#4
0x580106b6
#5
execOrders
#6
0x5acec890
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x0c7abd22
#2
0x9ac0761c
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
0x4e7bf95b…91d3
0xf42df8…ad97
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xf42fcae0…ddd1
0x34b655…2a6f
4 touches
1 conflict
0x1b458e47…5ab5
0x34b655…2a6f
4 touches
1 conflict
0xac7747f6…0550
0x34b655…2a6f
3 touches
1 conflict
0x093832b8…f1a9
0x34b655…2a6f
3 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:
0xf42df81a…61ad97
1 conflict on slot
0x4e7bf95bac…6491d3
Audit this contract →
← previous block
·
next block →
recent activity