pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,491,097
← previous block
next block →
recent activity
Analyzing
Block #112,491,097
13 transactions · 11 stateful · 2026-10-11 14:21:28 UTC
Parallelism
85
/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,491,097
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x32d01e04
#3
0x32d01e04
#4
0x59558d29
#5
0xab083028
#6
0x580106b4
#7
0x5acec890
#8
0x5acec890
#9
0x84403c1b
· blocks 1
#11
execFwdPositionOpsV2
#12
setData
#10
0x84403c1b
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
0x36a76bd2…1fb0
0x34b655…2a6f
4 touches
1 conflict
0xb8f43c8d…77b2
0x34b655…2a6f
4 touches
1 conflict
0xbcc2ea3e…8ea3
0x34b655…2a6f
4 touches
1 conflict
0xce84e9bc…1b54
0x34b655…2a6f
4 touches
1 conflict
0xdf814687…1391
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
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:
Perpl
1 conflict on slot
0x36a76bd264…b01fb0
Audit this contract →
← previous block
·
next block →
recent activity