pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#111,831,709
← previous block
next block →
recent activity
Analyzing
Block #111,831,709
14 transactions · 12 stateful · 2026-10-09 07:03:51 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#111,831,709
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x5acec890
#3
execOrders
· blocks 1
#5
execPerpOps
#6
execPerpOps
#7
0xaf47a8bb
#8
0x3f5c179b
#9
executeBatch
#10
forward
#11
0x57368ddf
#12
0x2921b7…3146
#13
setData
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01614992…09b3
0x34b655…2a6f
2 touches
0 conflicts
0x01a9679e…1740
0x34b655…2a6f
2 touches
0 conflicts
0x029aec48…e330
0x34b655…2a6f
2 touches
0 conflicts
0x0d8a97d7…b5d8
0x34b655…2a6f
2 touches
0 conflicts
0x10937365…9aff
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