pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,230,082
← previous block
next block →
recent activity
Analyzing
Block #100,230,082
9 transactions · 8 stateful · 2026-08-29 16:18:47 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,230,082
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
execOrders
#4
updatePrices
#5
setData
#6
execFwdPositionOpsV2
· blocks 1
#7
execOrders
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x24104c4d…3a3a
0x068f22…7908
2 touches
0 conflicts
0xf91620c4…d3ca
0x068f22…7908
2 touches
0 conflicts
0x0e6850fc…ff99
0x09475a…400f
2 touches
0 conflicts
0xbc634819…e116
0x09475a…400f
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
0xb9b4eff6b7…8cc3ef
Audit this contract →
← previous block
·
next block →
recent activity