pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,586,411
← previous block
next block →
recent activity
Analyzing
Block #100,586,411
10 transactions · 8 stateful · 2026-08-30 22:15:19 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,586,411
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x928e4afa
· blocks 1
#3
0x59558d29
#4
execOrders
#6
execFwdPositionOpsV2
#7
setData
#8
0x3f5c179b
#9
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b10f1de…fc43
0x34b655…2a6f
2 touches
0 conflicts
0x2a9c85c8…bbb4
0x34b655…2a6f
2 touches
0 conflicts
0x2aae51a6…8f07
0x34b655…2a6f
2 touches
0 conflicts
0x3d4584df…ffed
0x34b655…2a6f
2 touches
0 conflicts
0x487cf2b0…1dfb
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
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity