pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,573,593
← previous block
next block →
recent activity
Analyzing
Block #84,573,593
10 transactions · 9 stateful · 2026-06-30 00:36:57 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,573,593
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x77813803
· blocks 1
#4
0x0f6795d9
#5
0x0f6795d9
#7
0x6a431021
#8
setData
#9
0x39435dac
#6
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x244fd533…2236
0x1efe02…37d6
2 touches
0 conflicts
0x3b21cfd4…174d
0x1efe02…37d6
2 touches
0 conflicts
0x4524699c…80d2
0x1efe02…37d6
2 touches
0 conflicts
0xc6382dc8…0766
0x1efe02…37d6
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:
LeverUp: LeverUp
1 conflict on slot
0xa8abcc1955…203d83
Audit this contract →
← previous block
·
next block →
recent activity