pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,990,625
← previous block
next block →
recent activity
Analyzing
Block #97,990,625
8 transactions · 7 stateful · 2026-08-21 19:30:34 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,990,625
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8263f5d9
#2
execOrders
#3
execFwdPositionOpsV2
#4
0x4b6bcf…eaa6
#5
0x61d59c2d
· blocks 1
#7
execOrders
#6
swapExactTokensForTokens
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f3fc53…7c13
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf2
0x77d53b…8080
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
2 touches
0 conflicts
0x1408e7c7…f324
0x34b655…2a6f
2 touches
0 conflicts
0x33e01acb…8838
0x34b655…2a6f
2 touches
0 conflicts
0x469dac8d…3411
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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:
0x77d53b3b…378080
1 conflict on slot
0xa4f3fc535b…ee7c13
Audit this contract →
← previous block
·
next block →
recent activity