pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,123,651
← previous block
next block →
recent activity
Analyzing
Block #100,123,651
12 transactions · 11 stateful · 2026-08-29 07:22:53 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,123,651
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
forward
#3
execPerpOps
#4
execPerpOps
#5
setData
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x94defb17
· blocks 1
#10
execFwdPositionOpsV2
#11
0x6a928945
#9
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cccbb7…1307
0x8964d7…10f8
4 touches
1 conflict
0x46cccbb7…1308
0x8964d7…10f8
4 touches
1 conflict
0x46cccbb7…130b
0x8964d7…10f8
4 touches
1 conflict
0x46cccbb7…130c
0x8964d7…10f8
4 touches
1 conflict
0x46cccbb7…130e
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x5fad6fee…7714
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x46cccbb71e…e31307
Audit this contract →
← previous block
·
next block →
recent activity