pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,627,795
← previous block
next block →
recent activity
Analyzing
Block #81,627,795
11 transactions · 10 stateful · 2026-06-16 08:57:40 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,627,795
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
approve
· blocks 1
#4
permit2TransferAndMulticall
#5
updateDataFeedsValuesPartial
#6
updatePrices
· blocks 1
#8
setData
#9
0x6a31107c
#10
0x39435dac
#2
deposit
· blocks 1
#7
updatePrices
#3
0xa09e9040
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xd4bf85b2…3412
0x065c9d…c394
2 touches
0 conflicts
0xfe4e8f4a…5950
0x065c9d…c394
2 touches
0 conflicts
0xb1a0dd74…f087
0x188d58…ea8e
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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:
0xaa7ee7ce…aff0e4
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity