pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,743,473
← previous block
next block →
recent activity
Analyzing
Block #99,743,473
10 transactions · 8 stateful · 2026-08-27 23:24:41 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,743,473
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updatePrices
#3
execOrders
#4
0x5acec890
· blocks 1
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#7
setData
#8
0x3f5c179b
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b53436c…2ec3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01dc29d8…bcd2
0x34b655…2a6f
2 touches
0 conflicts
0x0ca0c007…c722
0x34b655…2a6f
2 touches
0 conflicts
0x168f75b5…b2d1
0x34b655…2a6f
2 touches
0 conflicts
0x2251dae7…715a
0x34b655…2a6f
2 touches
0 conflicts
0x35b89cd8…5092
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x3b53436c6f…c62ec3
Audit this contract →
← previous block
·
next block →
recent activity