pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,275,366
← previous block
next block →
recent activity
Analyzing
Block #85,275,366
12 transactions · 10 stateful · 2026-07-03 06:36:30 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
#85,275,366
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x13572d0b
· blocks 1
#2
0xab083028
#3
0x6ad2e98b
#4
0x39435dac
#5
updateDataFeedsValuesPartial
#6
0x62be7533
#7
0x0c7abd22
#8
forward
#9
0x6a4758e6
#10
setData
#11
____MEV_X____Ga543
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0002
0x023eb9…b2b4
4 touches
1 conflict
0x00000000…0004
0x023eb9…b2b4
4 touches
1 conflict
0x00000000…000c
0x023eb9…b2b4
4 touches
1 conflict
0x11c3ab2d…cd65
0x3bd359…433a
4 touches
1 conflict
0xbcc1b459…f94f
0x3bd359…433a
4 touches
1 conflict
0x3931dd58…c7f4
0x405b63…7777
4 touches
1 conflict
0xa74cd79c…705a
0x405b63…7777
4 touches
1 conflict
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:
0xaa5de197…a1d330
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity