pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,024,919
← previous block
next block →
recent activity
Analyzing
Block #84,024,919
13 transactions · 11 stateful · 2026-06-27 11:40:12 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,024,919
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
0x5a5d9a99
#4
executeBatch
· blocks 1
#6
0x0f6795d9
#7
0xed82b078
#8
0xed82b078
#9
0x0f6795d9
#10
updateDataFeedsValuesPartial
#11
0x6a3fb714
#12
setData
#5
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x532023a5…d800
0xe52b14…7230
4 touches
1 conflict
0x5149ba0e…d954
0x754704…b603
4 touches
1 conflict
0x0b0c2e8d…c1b8
0xe52b14…7230
4 touches
1 conflict
0x09a15b10…2639
0x754704…b603
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xada23efa…223d
0xe52b14…7230
3 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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:
0xe52b1424…bb7230
1 conflict on slot
0x532023a546…d6d800
Audit this contract →
← previous block
·
next block →
recent activity