pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,612,061
← previous block
next block →
recent activity
Analyzing
Block #112,612,061
12 transactions · 12 stateful · 2026-10-12 00:30:05 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,612,061
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
execOrders
· blocks 1
#4
0x5acec890
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
updateDataFeedsValuesPartial
#9
0x3f5c179b
#10
setData
#11
execOrders
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85cec0eb…da3b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x1b9a2914…75cc
0x34b655…2a6f
2 touches
0 conflicts
0x2ac4cf3c…ec38
0x34b655…2a6f
2 touches
0 conflicts
0x36ff4a21…68b0
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
0x85cec0eb03…77da3b
Audit this contract →
← previous block
·
next block →
recent activity