pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,873,266
← previous block
next block →
recent activity
Analyzing
Block #100,873,266
10 transactions · 10 stateful · 2026-08-31 22:18:43 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,873,266
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
execOrders
#4
0x59558d29
#5
executeBatch
· blocks 1
#7
setData
#8
execFwdPositionOpsV2
#9
0x6a95fe3b
#6
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57070322…bc66
0xe52b14…7230
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf275b4ca…57b8
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x15c6ded9…48e7
0x754704…b603
2 touches
0 conflicts
0x5a7e4e98…1f3b
0x754704…b603
2 touches
0 conflicts
0xd4c946a4…b8d4
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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:
0xe52b1424…bb7230
1 conflict on slot
0x570703220d…6ebc66
Audit this contract →
← previous block
·
next block →
recent activity