pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,288,341
← previous block
next block →
recent activity
Analyzing
Block #99,288,341
11 transactions · 10 stateful · 2026-08-26 09:04:06 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,288,341
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x8263f5d9
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
execFwdPositionOpsV2
#7
forward
#8
setData
#9
0x61d59c2d
· blocks 1
#10
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3abe489…ec0e
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a0d
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf2
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf3
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf5
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf6
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ec0b
0x77d53b…8080
4 touches
1 conflict
0x066903bd…c1b4
0x77d53b…8080
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:
0x77d53b3b…378080
1 conflict on slot
0xe3abe4895e…e5ec0e
Audit this contract →
← previous block
·
next block →
recent activity