pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,573,845
← previous block
next block →
recent activity
Analyzing
Block #89,573,845
10 transactions · 10 stateful · 2026-07-23 05:21:29 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,573,845
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
cancel
#5
0x0f6795d9
· blocks 1
#8
setData
#9
0x39435dac
#6
0x0f6795d9
· blocks 1
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd6c0349d…05b0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x0ae5298c…53ce
0x34b655…2a6f
2 touches
0 conflicts
0x1c21cfff…6ba1
0x34b655…2a6f
2 touches
0 conflicts
0x1e5833fa…ec25
0x34b655…2a6f
2 touches
0 conflicts
0x1fbd24c7…325b
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