pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,368,277
← previous block
next block →
recent activity
Analyzing
Block #99,368,277
13 transactions · 12 stateful · 2026-08-26 15:46:30 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,368,277
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
0x59558d29
· blocks 1
#5
execPerpOps
#6
execPerpOps
#7
withdraw
#8
execFwdPositionOpsV2
#9
0x3f5c179b
#10
0x6a8f0ace
#11
setData
#12
withdraw
#4
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x1c7a21bc…03ea
0x34b655…2a6f
2 touches
0 conflicts
0x297de2d5…7396
0x34b655…2a6f
2 touches
0 conflicts
0x2aab0897…78f7
0x34b655…2a6f
2 touches
0 conflicts
0x32164862…19d1
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…00004b
Audit this contract →
← previous block
·
next block →
recent activity