pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,122,278
← previous block
next block →
recent activity
Analyzing
Block #99,122,278
10 transactions · 9 stateful · 2026-08-25 19:08:34 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,122,278
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
setData
#2
execOrders
· blocks 1
#4
0x59558d29
#5
executeBatch
#7
0xed82b078
#8
execOrders
#9
execOrders
#3
execOrders
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x043fd7a0…bb94
0x34b655…2a6f
2 touches
0 conflicts
0x33000c0a…82c3
0x34b655…2a6f
2 touches
0 conflicts
0x3542128c…f6c4
0x34b655…2a6f
2 touches
0 conflicts
0x4188cc5f…2d2e
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity