pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,580,793
← previous block
next block →
recent activity
Analyzing
Block #112,580,793
13 transactions · 11 stateful · 2026-10-11 21:52:46 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,580,793
· 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
execOrders
· blocks 1
#7
execOrders
#8
execOrders
#10
forward
#11
forward
#12
setData
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x170c6832…977c
0x34b655…2a6f
2 touches
0 conflicts
0x2328941c…84d3
0x34b655…2a6f
2 touches
0 conflicts
0x318f9d69…8130
0x34b655…2a6f
2 touches
0 conflicts
0x6ab46c0d…930f
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity