pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,290,530
← previous block
next block →
recent activity
Analyzing
Block #99,290,530
11 transactions · 10 stateful · 2026-08-26 09:15:07 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,290,530
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6d7848b5
· blocks 1
#2
matchOrders
#3
updatePrices
#4
updatePrices
#5
0xab083028
#6
0x59558d29
#7
0x3f5c179b
#8
execFwdPositionOpsV2
#9
setData
#10
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3abe489…ebf3
0x77d53b…8080
4 touches
1 conflict
0x7e32f1e0…5612
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a26
0x77d53b…8080
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0xebaa354d…2fb7
0x3bd359…433a
2 touches
0 conflicts
0x02f4f6e2…47c6
0x754704…b603
2 touches
0 conflicts
0x0449d018…e334
0x754704…b603
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:
0x77d53b3b…378080
1 conflict on slot
0xe3abe4895e…e5ebf3
Audit this contract →
← previous block
·
next block →
recent activity