pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,193,654
← previous block
next block →
recent activity
Analyzing
Block #84,193,654
12 transactions · 9 stateful · 2026-06-28 06:23:44 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,193,654
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
multicall
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
0x98717539
#6
0x0f6795d9
· blocks 1
#7
0x6a40be68
#8
0x92acfa…277a
#9
setData
#11
0x39435dac
#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
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0010
0x69d57b…cc2f
2 touches
0 conflicts
0x03a13418…2786
0x69d57b…cc2f
2 touches
0 conflicts
0x953a5a37…ae17
0x69d57b…cc2f
2 touches
0 conflicts
0xdd689e37…5813
0x69d57b…cc2f
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