pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#116,289,014
← previous block
next block →
recent activity
Analyzing
Block #116,289,014
11 transactions · 11 stateful · 2026-10-24 21:19:51 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#116,289,014
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x35e534ea
#3
0x5acec890
#4
0x5acec890
#5
execOrders
· blocks 1
#7
0xa96df62f
#8
updatePrices
#9
execOrders
#10
setData
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
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
0x00da2c8a…f644
0x34b655…2a6f
2 touches
0 conflicts
0x1f00a5b3…bf76
0x34b655…2a6f
2 touches
0 conflicts
0x2ce2d2eb…23b3
0x34b655…2a6f
2 touches
0 conflicts
0x2d3f0d39…f1c7
0x34b655…2a6f
2 touches
0 conflicts
0x52df67cf…f77b
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