pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,276,091
← previous block
next block →
recent activity
Analyzing
Block #102,276,091
12 transactions · 11 stateful · 2026-09-05 20:11:16 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
#102,276,091
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
· blocks 1
#3
approve
· blocks 1
#5
0x57368ddf
#6
forward
#7
execFwdPositionOpsV2
#8
transferWithAuthorization
#9
0x6a9c7766
#10
0x36326531
#11
execOrders
#2
swap
#4
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b9e2d47…9675
0x188d58…ea8e
4 touches
1 conflict
0x38aa1898…fdf5
0xb53c4f…8a01
4 touches
1 conflict
0x9050c757…37cc
0xb53c4f…8a01
4 touches
1 conflict
0x1342557a…df31
0x27bc99…9a93
4 touches
1 conflict
0xb3dee783…2711
0x27bc99…9a93
4 touches
1 conflict
0x17359e55…7914
0x188d58…ea8e
4 touches
1 conflict
0xd193c581…5914
0x350035…7777
2 touches
1 conflict
0x692a4122…76b8
0x350035…7777
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:
Uniswap: PoolManager
1 conflict on slot
0x8b9e2d473e…1c9675
Audit this contract →
← previous block
·
next block →
recent activity