pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,142,496
← previous block
next block →
recent activity
Analyzing
Block #100,142,496
13 transactions · 12 stateful · 2026-08-29 08:57:54 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,142,496
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x5acec890
#4
0x59558d29
#5
0x59558d29
#6
executeBatch
· blocks 1
#8
setData
#9
execFwdPositionOpsV2
#10
bet
#11
execOrders
· blocks 1
#7
executeBatch
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf4ff2ba1…90a3
0xe52b14…7230
3 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x76c4467d…ce28
0x34b655…2a6f
2 touches
0 conflicts
0xfcaee83d…428d
0x34b655…2a6f
2 touches
0 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity