pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,083,473
← previous block
next block →
recent activity
Analyzing
Block #100,083,473
12 transactions · 10 stateful · 2026-08-29 04:00:35 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,083,473
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
0x5acec890
· blocks 1
#4
0x928e4afa
#5
execOrder
#6
0x59558d29
#7
setData
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
0x6a9259da
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0x378f46e4…4766
0x34b655…2a6f
4 touches
1 conflict
0xf79f04fe…a715
0x34b655…2a6f
4 touches
1 conflict
0x1f00a5b3…bf76
0x34b655…2a6f
2 touches
0 conflicts
0x238834f3…3f06
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x68297b76…8e24
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
0xa457c06e58…312f06
Audit this contract →
← previous block
·
next block →
recent activity