pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,407,673
← previous block
next block →
recent activity
Analyzing
Block #81,407,673
8 transactions · 7 stateful · 2026-06-15 08:31:15 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,407,673
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePriceFeedsIfNecessary
#2
0x3f5c179b
#3
0x6df9e92b
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x634daab4…dd5e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2549dda6…9e24
0x34b655…2a6f
4 touches
1 conflict
0x12117fd0…ec1a
0xb754ba…508d
2 touches
0 conflicts
0x12117fd0…ec1b
0xb754ba…508d
2 touches
0 conflicts
0x1232a81d…88d7
0xb754ba…508d
2 touches
0 conflicts
0x1232a81d…88d8
0xb754ba…508d
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
0x634daab4a2…5edd5e
Audit this contract →
← previous block
·
next block →
recent activity