pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,284,565
← previous block
next block →
recent activity
Analyzing
Block #99,284,565
12 transactions · 11 stateful · 2026-08-26 08:45:07 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,284,565
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
0x59558d29
#4
execFwdPositionOpsV2
· blocks 1
#5
execOrders
#7
0x6a8ea80a
#8
setData
#9
0x61d59c2d
· blocks 1
#11
execOrders
#6
execFwdPositionOpsV2
#10
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc9520be…83a3
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebfd
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ec09
0x77d53b…8080
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x467e524d…39c9
0x77d53b…8080
4 touches
1 conflict
0x7e32f1e0…5612
0x77d53b…8080
4 touches
1 conflict
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
0xfc9520be1c…7083a3
Audit this contract →
← previous block
·
next block →
recent activity