pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,698,540
← previous block
next block →
recent activity
Analyzing
Block #90,698,540
9 transactions · 8 stateful · 2026-07-27 06:20:21 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,698,540
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x98c6107a
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
setData
#3
0x98c6107a
· blocks 1
#4
0x98c6107a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ed742f…63f5
0x3bd359…433a
6 touches
3 conflicts
0x4eb758b8…b13b
0x3bd359…433a
6 touches
3 conflicts
0x67d846dd…358c
0x609679…7777
6 touches
3 conflicts
0x02059d37…b643
0x9f3832…4ae4
6 touches
3 conflicts
0x02059d37…b644
0x9f3832…4ae4
6 touches
3 conflicts
0x6faf6baf…150d
0x9f3832…4ae4
6 touches
3 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
6 touches
3 conflicts
0x12a9b76e…cb76
0x3bd359…433a
6 touches
3 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:
Wrapped MON (WMON)
3 conflicts on slot
0x44ed742f98…3963f5
Audit this contract →
← previous block
·
next block →
recent activity