pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,989,558
← previous block
next block →
recent activity
Analyzing
Block #75,989,558
12 transactions · 10 stateful · 2026-05-21 06:20:22 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,989,558
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
exactInputSingle
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0xed82b078
#7
forward
#8
setData
#9
0x4059c5…df17
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0xb7c8652f…ebce
0x1111b3…4111
2 touches
0 conflicts
0xff68ee4c…37e3
0x1111b3…4111
2 touches
0 conflicts
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
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
0x18978822b6…2c2623
Audit this contract →
← previous block
·
next block →
recent activity