pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,241,935
← previous block
next block →
recent activity
Analyzing
Block #99,241,935
13 transactions · 12 stateful · 2026-08-26 05:10:34 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,241,935
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0756e95c
#2
execOrders
#3
0x5acec890
#4
execOrders
· blocks 1
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
report
#10
0x6a8e75c2
#11
setData
#12
execOrders
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xcc5da6ea…c1e5
0x34b655…2a6f
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x0f8965bb…e238
0x34b655…2a6f
2 touches
0 conflicts
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x1db5837f…1264
0x34b655…2a6f
2 touches
0 conflicts
0x63f4382e…57b6
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
0x7de579746e…f0f5ba
Audit this contract →
← previous block
·
next block →
recent activity