pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#116,896,598
← previous block
next block →
recent activity
Analyzing
Block #116,896,598
11 transactions · 9 stateful · 2026-10-27 00:18:23 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#116,896,598
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
#2
0x59558d29
#3
0x35e534ea
#4
0x5acec890
· blocks 2
#6
0x80419567
#7
execFwdPositionOpsV2
#8
setData
#10
0x0c7abd22
#5
0x5acec890
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1d4f817f…58f5
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3ab7acf6…be32
0x264123…670e
2 touches
0 conflicts
0x78793bd5…bc7f
0x264123…670e
2 touches
0 conflicts
0x7a77ed5b…9d06
0x264123…670e
2 touches
0 conflicts
0x947d8e81…ffeb
0x264123…670e
2 touches
0 conflicts
0xb8daa721…cf97
0x264123…670e
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity