pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,198,210
← previous block
next block →
recent activity
Analyzing
Block #76,198,210
9 transactions · 7 stateful · 2026-05-22 05:30:21 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,198,210
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x98717539
#3
exactInputSingle
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
setData
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebadaba6…8cc5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2f8cadb3…8dd0
0x065c9d…c394
2 touches
0 conflicts
0x3de4fb55…6bc6
0x065c9d…c394
2 touches
0 conflicts
0x64b55394…87f2
0x065c9d…c394
2 touches
0 conflicts
0xec3e68da…1fe6
0x065c9d…c394
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
0xebadaba615…ad8cc5
Audit this contract →
← previous block
·
next block →
recent activity