pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#117,049,577
← previous block
next block →
recent activity
Analyzing
Block #117,049,577
11 transactions · 9 stateful · 2026-10-27 13:09:08 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
#117,049,577
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
· blocks 1
#3
0x6450738f
· blocks 1
#5
0x5acec890
#6
execPerpOps
#7
execFwdPositionOpsV2
#8
transferWithAuthorization
#9
setData
#10
execOrders
#2
0x6450738f
#4
0x35e534ea
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b144b6…da03
0xc9de99…405d
4 touches
1 conflict
0xc2575a0e…f805
0x9d2963…5798
4 touches
1 conflict
0xc2575a0e…0480
0x9d2963…5798
4 touches
1 conflict
0xc2575a0e…04e2
0x9d2963…5798
4 touches
1 conflict
0xc2575a0e…f805
0xc9de99…405d
4 touches
1 conflict
0xc2575a0e…f92a
0xc9de99…405d
4 touches
1 conflict
0xc6b144b6…da00
0xc9de99…405d
4 touches
1 conflict
0xc6b144b6…da01
0xc9de99…405d
4 touches
1 conflict
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:
0xc9de998e…86405d
1 conflict on slot
0xc6b144b6c6…14da03
Audit this contract →
← previous block
·
next block →
recent activity