pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,370,323
← previous block
next block →
recent activity
Analyzing
Block #112,370,323
12 transactions · 11 stateful · 2026-10-11 04:13:50 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,370,323
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x32d01e04
#3
0x59558d29
#4
execOrders
#5
0x5acec890
#6
0x5acec890
#7
0x57368ddf
#8
setData
#9
0x61d59c2d
· blocks 1
#11
execOrders
#10
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c6
0x508254…98bd
4 touches
1 conflict
0x46344427…7ef0
0x508254…98bd
4 touches
1 conflict
0x4ea2b33b…7dbc
0x508254…98bd
4 touches
1 conflict
0x6c04daad…1130
0x508254…98bd
4 touches
1 conflict
0x822abf1b…c658
0x508254…98bd
4 touches
1 conflict
0x822abf1b…c65d
0x508254…98bd
4 touches
1 conflict
0x6235638c…6438
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
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