pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,841,485
← previous block
next block →
recent activity
Analyzing
Block #107,841,485
13 transactions · 9 stateful · 2026-09-25 08:09:01 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,841,485
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9ac0761c
#2
0x9ac0761c
· blocks 1
#3
0xab083028
#5
execFwdPositionOpsV2
#6
relay
#7
setData
#8
0x61d59c2d
#9
0x61d59c2d
#10
0x61d59c2d
#11
0x61d59c2d
#12
0x61d59c2d
#4
0x3e2e8792
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0a8c7a5…3422
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2fbf2475…bbc3
0x34b655…2a6f
2 touches
0 conflicts
0x3b040a12…3ac7
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x53fbb065…b406
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
0xa0a8c7a55a…e73422
Audit this contract →
← previous block
·
next block →
recent activity