pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,748,930
← previous block
next block →
recent activity
Analyzing
Block #89,748,930
9 transactions · 8 stateful · 2026-07-23 22:21:19 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,748,930
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0xce1e7030
· blocks 1
#6
setData
#7
0x6a629457
#8
0x39435dac
#5
0xce1e7030
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
0x449423ba…1e0d
0xe7a4f9…4b2d
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x1e3c1e00…440c
0x2a68ba…90c5
4 touches
1 conflict
0x864a48ae…c15c
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xddc22bc2…7f7a
0x754704…b603
4 touches
1 conflict
0x89a4b49b…960e
0xe7a4f9…4b2d
4 touches
1 conflict
0x4117b8c6…2a24
0x065c9d…c394
4 touches
1 conflict
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:
0xe7a4f903…1e4b2d
1 conflict on slot
0x449423baa8…841e0d
Audit this contract →
← previous block
·
next block →
recent activity