pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,174,106
← previous block
next block →
recent activity
Analyzing
Block #82,174,106
12 transactions · 9 stateful · 2026-06-18 21:41:17 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,174,106
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6df9e92b
· blocks 1
#4
0x9609049f
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x3f5c179b
#9
0x3f5c179b
#10
setData
#11
execOrders
#3
0x6df9e92b
#5
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x8fa7a69c…8fd7
0x46bd38…7777
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0x635321e6…3122
0xa7283d…0ace
4 touches
1 conflict
0x635321e6…3123
0xa7283d…0ace
4 touches
1 conflict
0x635321e6…3124
0xa7283d…0ace
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:
Wrapped Ether (WETH)
1 conflict on slot
0x56a919c43e…27ab49
Audit this contract →
← previous block
·
next block →
recent activity