pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,226,112
← previous block
next block →
recent activity
Analyzing
Block #90,226,112
10 transactions · 10 stateful · 2026-07-25 14:28:46 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,226,112
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#6
0x57368ddf
#7
updateDataFeedsValuesPartial
#8
0x6a64c895
#9
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0181bb37…6629
0x34b655…2a6f
4 touches
1 conflict
0xa897619a…879f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf06cb710…1a9a
0x34b655…2a6f
4 touches
1 conflict
0x86c98782…f3b7
0x34b655…2a6f
4 touches
1 conflict
0x0b7819b1…6672
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x19439a65…eb51
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x0181bb3798…ed6629
Audit this contract →
← previous block
·
next block →
recent activity