pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,344,526
← previous block
next block →
recent activity
Analyzing
Block #112,344,526
13 transactions · 13 stateful · 2026-10-11 02:04:02 UTC
Parallelism
85
/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,344,526
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x32d01e04
#2
0x59558d29
#3
0xab083028
#4
0x5acec890
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
0x5acec890
#9
execOrders
#10
0x84403c1b
· blocks 1
#12
setData
#11
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x9008a321…472b
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x1ee8aa48…d2ce
0x34b655…2a6f
2 touches
0 conflicts
0x42417880…b7b5
0x34b655…2a6f
2 touches
0 conflicts
0x4fb22186…c457
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
0x7aad02c682…feb979
Audit this contract →
← previous block
·
next block →
recent activity