pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,191,304
← previous block
next block →
recent activity
Analyzing
Block #102,191,304
5 transactions · 4 stateful · 2026-09-05 13:01:37 UTC
Parallelism
60
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,191,304
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 1
#4
execFwdPositionOpsV2
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf52c8c2a…fb4f
0x34b655…2a6f
3 touches
1 conflict
0xce06a0f7…efef
0x34b655…2a6f
3 touches
1 conflict
0x62811193…186c
0x34ae4d…3fc5
2 touches
0 conflicts
0xed5a2f84…19b3
0x34ae4d…3fc5
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
0x1db5837f6b…d01264
Audit this contract →
← previous block
·
next block →
recent activity