pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,726,853
← previous block
next block →
recent activity
Analyzing
Block #100,726,853
10 transactions · 9 stateful · 2026-08-31 10:01:48 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,726,853
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
· blocks 1
#4
0x59558d29
#5
0x59558d29
#6
execOrders
· blocks 2
#7
setData
#3
execOrders
#8
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27b6010e…e4aa
0x34b655…2a6f
6 touches
3 conflicts
0x20fb9049…c975
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x35b29270…6558
0x34b655…2a6f
2 touches
0 conflicts
0x35e29426…121c
0x34b655…2a6f
2 touches
0 conflicts
0x38d6111f…33a0
0x34b655…2a6f
2 touches
0 conflicts
0x69d6753e…a54e
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
3 conflicts on slot
0x27b6010e94…34e4aa
Audit this contract →
← previous block
·
next block →
recent activity