pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,722,708
← previous block
next block →
recent activity
Analyzing
Block #100,722,708
12 transactions · 10 stateful · 2026-08-31 09:40:57 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,722,708
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
· blocks 1
#4
0x59558d29
#5
0x59558d29
#6
executeBatch
· blocks 1
#8
execFwdPositionOpsV2
#9
0x57368ddf
#10
execFwdPositionOpsV2
#11
execOrders
#3
0xab083028
#7
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x86c18286…230d
0xe52b14…7230
3 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0x8a63fdf4…38ad
0x065c9d…c394
2 touches
0 conflicts
0xa1f1b040…4c83
0x065c9d…c394
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
0x8ffa332881…c9ce11
Audit this contract →
← previous block
·
next block →
recent activity