pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,400,289
← previous block
next block →
recent activity
Analyzing
Block #84,400,289
11 transactions · 11 stateful · 2026-06-29 05:20:56 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,400,289
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
transferETH
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x0f6795d9
· blocks 1
#7
forward
#8
0x0f6795d9
#9
setData
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xde17727d…26b5
0x065c9d…c394
2 touches
0 conflicts
0xbd7a4ed7…cd2c
0x194b12…cac0
2 touches
0 conflicts
0x7c25289a…0420
0x1d6f4d…1781
2 touches
0 conflicts
0x91d230bc…3489
0x1d6f4d…1781
2 touches
0 conflicts
0xad78307a…7a76
0x1d6f4d…1781
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
0xffc2f21efe…ecb393
Audit this contract →
← previous block
·
next block →
recent activity