pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#116,913,266
← previous block
next block →
recent activity
Analyzing
Block #116,913,266
14 transactions · 11 stateful · 2026-10-27 01:42:16 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#116,913,266
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
· blocks 1
#3
execOrders
#4
0x35e534ea
#5
0x5acec890
#6
0x5acec890
#7
0xb5ce855a
#8
execPerpOps
#9
execPerpOps
#10
0x80419567
#11
execFwdPositionOpsV2
#12
transferWithAuthorization
#13
setData
#2
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0016
0x80c745…7210
4 touches
1 conflict
0x00000000…0002
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x314b842f…76a1
0x34b655…2a6f
2 touches
0 conflicts
0x438bd4ad…ad2d
0x34b655…2a6f
2 touches
0 conflicts
0x46cb714c…a3d9
0x34b655…2a6f
2 touches
0 conflicts
0x5b70fd51…a733
0x34b655…2a6f
2 touches
0 conflicts
0x61e0df38…b7d2
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…000016
Audit this contract →
← previous block
·
next block →
recent activity