pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,475,710
← previous block
next block →
recent activity
Analyzing
Block #112,475,710
12 transactions · 10 stateful · 2026-10-11 13:04:03 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,475,710
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
0x59558d29
#5
0x59558d29
#6
0x32d01e04
#7
0x5acec890
#8
updatePrices
#9
updateDataFeedsValuesPartial
#10
setData
#11
execOrders
#2
0x9ac0761c
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2aa8cd69…03b6
0xf42df8…ad97
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x6235638c…643a
0x1b6862…e19c
4 touches
1 conflict
0xad8d0be5…618b
0xd32edf…ff58
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
0x2aa8cd69a4…5203b6
Audit this contract →
← previous block
·
next block →
recent activity