pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,751,676
← previous block
next block →
recent activity
Analyzing
Block #89,751,676
9 transactions · 8 stateful · 2026-07-23 22:35:11 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,751,676
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
revealWithCallback
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
transfer
· blocks 1
#8
setData
#5
0x0f6795d9
#7
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x0af4a0c5…c070
0x34b655…2a6f
2 touches
0 conflicts
0x0bbc9941…4358
0x34b655…2a6f
2 touches
0 conflicts
0x0be7402c…b3c8
0x34b655…2a6f
2 touches
0 conflicts
0x0ddfdaf2…9e00
0x34b655…2a6f
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity