pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,709,639
← previous block
next block →
recent activity
Analyzing
Block #99,709,639
8 transactions · 8 stateful · 2026-08-27 20:33:36 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,709,639
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updatePrices
#3
0x59558d29
#5
setData
#6
0xed82b078
#4
0x0c7abd22
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2caeb7f5…b6bb
0x34b655…2a6f
4 touches
1 conflict
0x8b780b26…f5ff
0x34b655…2a6f
4 touches
1 conflict
0xc82512c0…8847
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x2fbf2475…bbc3
0x34b655…2a6f
2 touches
0 conflicts
0x478bc4fa…d060
0x34b655…2a6f
2 touches
0 conflicts
0x53e056e3…c862
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:
Perpl
1 conflict on slot
0x2caeb7f5e5…18b6bb
Audit this contract →
← previous block
·
next block →
recent activity